Configure the start condition
A trigger may be based on a schedule, an incoming event, or an explicit request, depending on the workflow system. Check its filters, enablement state, and event source when expected runs are missing or unexpected runs appear.
Triggers commonly define the initial input available to a run. Validate that input before using it, and consider whether the source can deliver duplicate, delayed, or out-of-order events.
Make steps handle the run input
Steps process data, call services, branch, wait, or request approval after a run begins. Each step should have clear inputs and outputs so a failure can be located without confusing it with a trigger that never fired.
When debugging, first establish whether a run record exists. If not, investigate the trigger and event delivery; if it does, inspect the step history and outputs. This narrows the problem to the correct part of the workflow.