Workflow Troubleshooting

This page is for diagnosing the most common workflow issues from a user perspective before diving into backend internals.

A Scheduled Workflow Did Not Run Immediately

This is usually expected.

Interval-based scheduled workflows do not fire at creation time. They schedule the first run in the future based on the selected interval or wall-clock time.

Check:

• whether the workflow uses a Scheduled Trigger instead of a Manual Trigger
• whether the schedule card shows Live with a future next-run time
• whether you expected a listener but actually created a scheduled task

A Scheduled Task Looks Stuck on Due

A Due state means the task is ready or overdue relative to the current clock.

Check:

• whether the task is actually running right now
• whether it is a one-time schedule that should disappear after completion
• whether the scheduler is active and the app is still open

If the behavior seems wrong after that, inspect the developer-side scheduler notes in Workflow Engine Architecture.

Pause and Resume Changed the Timing

Current expected behavior is that pause/resume preserves remaining time.

If the task appears to restart a full interval after resume, treat that as a regression rather than normal behavior.

The Run Modal Appears When I Did Not Expect It

Wardian opens the modal when launch-time data is needed.

Check whether the workflow has:

• agent roles that need assignment
• a Manual Trigger input schema
• both of the above

If yes, the modal is working as designed.

My Workflow Became a Live Listener Instead of Running

That usually means the workflow was launched through a listener-style trigger.

Expected listener-style behavior:

• File Watcher and webhook-style workflows activate as live listeners
• scheduled workflows should not appear under live listeners
• manual workflows should run immediately instead of entering listener mode

A Scheduled Task Was Deleted but the Workflow Still Exists

This is expected.

Deleting a schedule removes the scheduled instance, not the workflow definition. The workflow remains available in the builder and library unless you delete the workflow itself.

I Created Two Schedules With the Same Workflow Name

This is also expected.

Wardian allows multiple scheduled instances of the same workflow. Distinguish them by:

• target summary
• role mappings
• schedule timing

A Node Exists in the Model but Not in the Builder

The workflow model currently includes a few reserved or partially wired node types.

If you see names like parallel, governance, tool, or subflow in exported data or internal references, confirm their current support level in Node Reference before assuming they are fully available.

Where to Go Next

For deeper debugging:

• user behavior and launch rules: Triggers
• scheduling behavior: Scheduled Runs
• node capabilities: Node Reference
• backend execution details: Workflow Engine Architecture
• builder internals: Visual Builder Architecture