This topic describes the basic concepts, properties, and history of an execution.
Terms
An execution is a single run of a flow. After you create a flow, you can run it multiple times. Each execution usually has a different input. For example, placing an order executes an order management flow, and the input for the execution is the order information.
Execution properties
The following list describes the properties of an execution. You provide the ExecutionName and Input to start an execution. The other properties are returned as output information.
- ExecutionName: The name of the execution. The name must be unique within the same flow and meet the following constraints:
- Can contain letters (a-z and A-Z), digits (0-9), underscores (_), and hyphens (-).
- Must start with a letter (a-z or A-Z) or an underscore (_).
- Is case-sensitive.
- Must be 1 to 128 characters long.
- Input: The input for the execution. The input must be in a JSON object format.
- Output: The output of the execution. The output must be in a JSON object format.
- FlowDefinition: The flow definition. For more information, see Flow Definition Language. To prevent flow updates from affecting running executions, each execution saves a copy of the flow definition that was active when it started.
- Status: The status of the execution. Valid values are Starting, Running, Stopped, Succeeded, Failed, and TimedOut.
- StartedTime: The time when the execution started.
- StoppedTime: The time when the execution ended.
Execution history events
A flow consists of multiple steps. As the flow runs, each step generates events that record its execution status in detail. These events provide information about the flow execution, such as the current step, input, output, duration, and failure reason. The Serverless Workflow service also uses this status data to track flow executions and ensure high availability.
The following list describes the properties of an execution event. The event details (EventDetail) are a string in a JSON object format. The content of the event details varies depending on the event type (Type).
- StepName: The name of the step. This corresponds to the step name in the Flow Definition Language.
- Type: The event type.
- EventDetail: The event details.
- Time: The time when the event occurred.
- EventId: The event ID.
- ScheduleEventId: The ID of the event that triggered the current event.