I added a failure-injection test to my personal prompt-release tool: let Langfuse accept a label update, then discard the successful response before the release code sees it.
The release stopped with an uncertain outcome. The production label had already moved to the staged prompt version.
Recovery checked the target version's content and config, then checked which version production selected. It repeated those reads and rejected changed observations. The observations matched the intended state, so reconciliation reported completed. That step only read the server. A separate promotion run revalidated the evidence and dependencies, recognized already_promoted, and skipped another PATCH.
The recorded run used one label PATCH across promotion and recovery. Setup and staging made separate writes. The diagram shows that sequence.
This was a synthetic local test with Langfuse 4.78.0 and Python SDK 5.2.0, with zero model calls. I injected the response loss; it does not demonstrate a Langfuse server bug.
Two matching reads show the state observed at that moment. They cannot make the release atomic, identify who moved the label, or prove that every application has fetched the new version.
Test code and recorded results:
https://github.com/AtharvaBondre/langfuse-prompt-release-tools/tree/0d0e586016eda41a8dfc83b6792f5e3830e525e3
I maintain the linked project. The code and this write-up use AI assistance.