Identifier handoff and result confirmation¶
Identifier |
Source |
Purpose |
|---|---|---|
Workflow application ID |
Workflow list/details |
Application operations such as Product SDK run and run lists |
workflow_version_id |
Deployed workflow version information |
Explicit target of Worker task POST |
task.id |
Successful Worker task POST response |
Mowl task identity; cannot read authoring drafts |
task.workflow_execution_id |
Same response |
Product execution details and result reads |
node_id + version |
Node catalog/current node |
Read exact custom operator source; operator_id is not an integer |
authoring task_id |
Agent workflow editing context |
Select task workspace draft source |
For an execution ID returned by Worker POST, product routes in the same environment register GET /workflow/v2/workflow-apps/executions/{execution_id} and its /result. Retain the same identity, workspace, and origin. Check that run’s state, errors, and actual outputs. Creation success or the SDK’s default ACTIVE value does not establish completion.
Product SDK application-level run and CLI workflow run remain ordinary developers’ existing task entry points. Do not replace them with Worker POST merely to increase route coverage. Source reads inspect code and are separate from operator test runs, workflow deployment, triggering, and result checks.