One execution identifier correlates the invocation with every poll
This single identifier is what makes an asynchronous round trip work through a synchronous invocation signature.
The rule
Normative: this is the rule
- An external invocation answers immediately with exactly one of three statuses:
completedfor a finished run,interruptedfor one paused awaiting an interrupt whose identifier the response carries, orqueued. - In all three cases the
execution_idit answers is the persisted run's identifier, the same value a poll response reports aspipeline_id. - An engine that answers a synthetic request identifier instead has its persisted identifier republished here, so the correlation identifier never varies by engine.
Rule identifiers are permanent and are never renumbered. Each implementation publishes its own standing against these rules; this specification does not.spec 1.0-draft · OCX-7 · changed in spec 1.0