Skip to content
English
Do you need help? Customer portal
neowit.io
  • There are no suggestions because the search field is empty.

Workflow didn't run

Your workflow should have fired but nothing happened. Here's how to narrow down why. For anyone expecting a workflow to run and finding it didn't.

First checks (90% of cases)

1. Is the workflow Enabled?

A disabled workflow doesn't receive real triggers. Open the workflow and check:

  • The Enabled toggle in the toolbar (next to the workflow name) should be on. Or open the Save Workflow dialog — Enabled is the third field.
  • If it's off, turn it on and save.

See Publishing and versions.

[SCREENSHOT] The workflow editor's top bar with the Enabled toggle on (green) next to the workflow name.

2. Is workflow enabled at the org level?

Admins may have paused the whole engine.

  • Workflows → Settings → Org policy → check that Enabled is on.

See Org policy.

3. Did the trigger's event actually happen?

A "Booking No-Show" workflow runs when a booking is marked no-show. If Neowit didn't observe the transition (the booking was deleted directly, or the no-show status was set outside Neowit), the trigger won't fire.

Cross-check the event in Neowit's own UI — e.g. for booking events, the booking's history tab should show the state change.

4. Is the trigger connected?

An orphan trigger (no downstream node) fires but goes nowhere. Open the workflow and confirm:

  • The trigger has at least one outgoing edge.
  • The edge leads into a node on the canvas (not into empty space).

Next checks

5. Does the execution exist but route to a dead branch?

Click any node and open the Executions tab. If you see recent rows but no message was sent:

  • Find an execution around the expected time.
  • Expand the row to see per-node status.
  • If a condition node's output says "false" (and that branch isn't connected to anything), the workflow correctly ran but was filtered out.

Fix: loosen the condition or check the field you're comparing against.

6. Does an action show "Error" status?

In the execution detail view, a red node means the action failed. Click into it for the error message.

Common causes:

  • Slack action failed — the target user's email isn't in the connected Slack workspace. See Slack.
  • Integration disconnected — the Slack or Hue integration's OAuth token expired. See Integration disconnected.
  • Template error — a reference in a message body pointed at data that didn't exist on this particular event.

[SCREENSHOT] Execution detail view showing three nodes: trigger (green), If (green), Send Slack DM (red with "error" label). An expandable details section under the red node shows the error message.

7. Did the schedule actually tick?

Schedule-triggered workflows only run if:

  • The org policy has a service account configured (see Org policy).
  • The service account is enabled and wasn't deleted.
  • The configured timezone and schedule math produced a "now" within the last minute.

Schedule triggers also need at least one node downstream of them — if the schedule trigger sits alone with nothing connected to its output, there's nothing to do.

Still stuck

If none of the above matches:

  • Note the workflow name and the expected event time.
  • Grab a screenshot of the workflow editor and the execution detail (or its absence).
  • Contact Neowit support — they can look at the server-side logs and trace from trigger through dispatch.

Related