Triggering and monitoring workflow runs
The ways a durable job is normally started, from an API call to a schedule to an event elsewhere, and what you need to see while a run is in progress.
What this covers
A workflow run is started in one of three ways: your own code calls the engine and hands it the input, a schedule starts it on a timer, or an event elsewhere in your system triggers it. Once running, the thing you need to see is not a log line but a state: which step it is on, which steps have already succeeded, how many times a step has been retried, and what the last error was. That view is what makes a stuck run diagnosable, because it tells you whether the job is progressing slowly or waiting on something that is never coming.
Workflows are not available on Voroa today. Work that runs on a timer can be scheduled as a task.