Trying to automate a deployment for a v2.14 SDK project. Calling /api/v2/flows/actions/checkout on a specific flow ID but keep hitting a 409 Conflict.
The flow isn’t locked by anyone else in the org. Tried running /api/v2/flows/actions/unlock first, but that returns a 404.
{
"message": "The requested resource was not found",
"code": "NOT_FOUND",
"status": 404
}
this 409 is classic. happens because flow is “ghost locked” in backend. docs don’t say it, but /api/v2/flows/actions/unlock returns 404 if you aren’t the one who locked it. very stupid.
try this - call revert first:
POST /api/v2/flows/actions/revert?flow=FLOW_ID
then try checkout again. is the only way i found.
The 409 Conflict happens because the flow is locked by another session.
I apologize if this is a beginner question, but does this “ghost lock” create a gap in the audit trail for SOC2? It’s worth a shot to check if the /api/v2/flows/actions/revert mentioned in the earlier reply removes the lock without leaving a record.