Skip to main content
WorkflowDog supports two scheduling patterns: Choose the trigger for recurring jobs such as a daily report. Choose the action for delayed work such as sending a follow-up two days after an event.

​
Example: send a daily report

Create a workflow with the Schedule trigger:
1

Choose the schedule

Add a daily schedule at the intended local time and confirm its timezone. A workflow can have multiple schedule entries.
2

Load the data

Add the actions that read the source system. Keep unrelated reads on independent branches when they can run concurrently.
3

Build the report

Combine the values into text, HTML, a spreadsheet, or a file. Use a sub-workflow when the same report logic is reused elsewhere.
4

Deliver and inspect

Add the send action, wait for the graph to save, enable the workflow, and inspect its next run in Run History.

​
Example: schedule a one-time follow-up

Create a second workflow with the Callable trigger. Give its trigger inputs the values the follow-up needs. In the first workflow:
  1. Add Schedule Workflow.
  2. Select the callable workflow.
  3. Set the future date and time.
  4. Connect the callable workflow’s inputs.
The scheduled execution appears in Run History. It already exists in the queue, so pausing the child workflow does not remove it. Cancel that scheduled run from history when it should no longer execute.
A delayed run uses the child workflow’s saved graph when it executes. Review scheduled work before making incompatible changes to the child’s expected trigger data.

​
Make schedules reliable

  • State the timezone explicitly; do not assume every teammate or service uses the same local time.
  • Design recurring work to tolerate being retried manually.
  • Avoid relying on one run’s in-memory state. Store durable state in the destination service or a project variable.
  • Add Succeeded? or Error meta outputs around critical delivery actions when a recovery branch is useful.
See Scheduling workflows for configuration details and Workflow runs for cancel and rerun behavior.