js-bao-wss-client / WorkflowStatusEvent
Interface: WorkflowStatusEvent
Payload of the workflowStatus event (client.on("workflowStatus", ...)). Delivered in real time when a workflow run started by this user reaches a terminal state. output carries the final result on completion, error the failure message, and needsApply signals that the result awaits the client-side apply step.
Properties
contextDocId?
optionalcontextDocId?:string
error?
optionalerror?:string
errorCode?
optionalerrorCode?:WorkflowRunErrorCode
Platform classification of a "failed" run — compare this to a constant instead of matching error text. Omitted on any non-failed status, and absent for a failure the platform did not classify.
meta?
optionalmeta?:Record<string,unknown>
needsApply?
optionalneedsApply?:boolean
output?
optionaloutput?:unknown
runId
runId:
string
runKey
runKey:
string
skipReason?
optionalskipReason?:"LOCK_CONTENTION"
Why a "skipped" run did not run. "LOCK_CONTENTION" means the run's declarative lock was held and the definition declared onContention: "ignore", so the platform elided the run instead of failing it. Omitted on any non-skipped status; a skipped frame carries no error.
startedByUserId?
optionalstartedByUserId?:string
status
status:
"completed"|"failed"|"terminated"|"skipped"
type
type:
"workflowStatus"
workflowId
workflowId:
string
workflowKey
workflowKey:
string