comet runtime

comet runtime dispatch reads a request file and returns structured results. A host can retain the same Run across processes and continue the current Action or user Wait.

Invocation

Use the complete package on the first call:

comet runtime dispatch --application-file ./local-report/application.json --project-root . --request start.json --json

Use the application identity and original Run afterward:

comet runtime dispatch --application local-report --project-root . --request request.json --json

Do not hand a Run to a different application identity or create another Run to repeat an external operation.

Common requests

operation	Purpose
`start`	Pin the workflow version and input, then start a Run
`inspect`	Read saved state, Actions, and Waits
`next`	Prepare the next step from dependencies and current state
`execute`	Execute the current pending Action through a configured port
`claim`	Claim the current Action for host execution
`record-outcome`	Report the original Action’s actual result
`resolve-wait`	Submit the current approval decision
`record-evidence`	Submit the declared actual evidence
`retry`	Retry along an allowed failure recovery path

A start request includes runId, workflow id/version, and business input. Action and Wait requests use the identities you actually read; do not guess them or reuse an outdated proposal.

Execution and waiting

{
  "operation": "execute",
  "runId": "<original-run-id>",
  "actionId": "<current-pending-action-id>",
  "executorId": "<configured-execution-port-id>"
}

Outputs are checked against Schemas, business validators, and application artifact contracts. completed means the declared path has ended. Read the actual business result as well: a report may have been published or may have ended along a rejection branch.

Integration boundaries

JSON requests do not load unregistered host capabilities or obtain user authorization. Supply credentials through the host execution context; do not put them in request files or persisted results. When an external result is unknown, query the original executor and external system before reporting or retrying based on evidence. See SDK recovery. For a complete report template, see Workflow Application.

Start authoring

Practical tutorials

Authoring and validation

Installation and recovery

Related commands

Invocation

Common requests

Execution and waiting

Integration boundaries

​Invocation

​Common requests

​Execution and waiting

​Integration boundaries

Invocation

Common requests

Execution and waiting

Integration boundaries