jargon

Platform & DevOps·Infrastructure described in a file

two people applied at once, and the second was refused rather than allowed to interleave writes into the same record.

State locking

Also calledlock, concurrent apply protection

Taking an exclusive lock on the state before an apply, so concurrent runs cannot corrupt it. It is what makes a shared pipeline safe and what produces the familiar 'state is locked' message when a previous run was killed halfway. Force-unlocking is the standard remedy and the standard way to cause the corruption the lock existed to prevent, so it deserves more suspicion than it usually gets.

Commonly confused with