Click or drag to resize

IDs & executions

Workflow executions are identified by a workflow ID. This can be any string you choose or Cadence will generate a UUID when you start the workflow. You can use the workflow ID to monitor the progress of you workflow and obtain its result. Cadence also tracks workflows using a second run ID. This is a Cadence generated UUID assigned whenever a workflow is rescheduled as CRON job or is continued as as a new workflow to prevent the history from growing without bound.

So the workflow ID identifies the workflow and the run ID identifies the last or current run of the workflow. It's often convienent to use workflow IDs that map to business entities. For example, if you want to have a lifetime value (LTV) workflow running for each of your customers you could set the workflow ID to customer-ltv-CUSTOMERID, where CUSTOMERID uniquely identifies the customer.

The workflow and run IDs are combined into WorkflowExecution type.

See Also