---
id: OCX-7
family: RT-OCX
level: core
profiles: [runtime]
posture: normative-target
added: "1.0"
changed: "1.0"
source: https://flowdrop.io/spec/rules/rt-ocx/ocx-7
specification: FlowDrop Workflow Specification 1.0-draft
licence: CC BY 4.0
---

# OCX-7 — One execution identifier correlates the invocation with every poll

*RT-OCX (Part II) · level: core · profiles: runtime · added in 1.0*

This single identifier is what makes an asynchronous round trip work through a synchronous invocation signature.

## The rule

> **Normative.** This is the rule.
>
> 1. An external invocation answers immediately with exactly one of three statuses: `completed` for a finished run, `interrupted` for one paused awaiting an interrupt whose identifier the response carries, or `queued`.
>
> 2. In all three cases the `execution_id` it answers is the persisted run's identifier, the same value a poll response reports as `pipeline_id`.
>
> 3. An engine that answers a synthetic request identifier instead has its persisted identifier republished here, so the correlation identifier never varies by engine.

## Related rules

- Names: OCX-4, OCX-8
- Referenced by: OCX-4

---

Rule identifiers are permanent and are never renumbered. This specification carries
no implementation status: each implementation publishes its own standing against
these rules. Licensed CC BY 4.0.