FileMaker Soft Lock — Record Locking Flow

FileMaker Soft Lock — Record Locking Flow A sequence diagram generated by Archify. Lock_Acquire {table,id,name,client,ttl} find/create + Open Record row held open = native lock =atomic transition row open OK check owner+expiry → write owner, token, TTL commit GRANTED {token, expires} · DENIED if held Lock_Renew {token} every ~30s verify token → extend expires commit RENEWED · LOST if token stale Record_Update_Guarded {token, modId, fields} open lock row, verify token Open Record (native lock) error 301 → IN_USE if a Pro editorholds it record open check modId+expected → write → commit commit → new modId OK {modId} · LOST · CONFLICT · IN_USE Lock_Release {token} clear owner fields (token must match) RELEASED Acquire Heartbeat Guarded write Release API / WebViewer client · Data API · OData · Sequence participant API / WebViewer client Data API · OData Lock_* scripts · FMS · full access · Sequence participant Lock_* scripts FMS · full access Record_Update_Guarded · guarded writer · Sequence participant Record_Update_Guarded guarded writer Locks table · lease + fencing token · Sequence participant Locks table lease + fencing token Data record · protected table · Sequence participant Data record protected table Legend main request return message