A workflow didn't run

Start here when you saved a record and the thing the workflow should do did not happen. First answer one question: is there a run? Open Automation on the module, find the workflow, and choose Runs. No run means it never started. A run means it started, so read Find out why a workflow failed instead.

The workflow is switched off

Check. On the Automation list, look at the switch in the ON column. On the Designer home, a workflow that is off shows an Off pill.

Fix. Turn the switch on. A turned-off workflow keeps its settings and history, so nothing is lost. A webhook call to a workflow that is off is answered with 400 and the message Flow is not active anymore.

An Adhoc workflow is started by a button or by another workflow. To stop people starting it, remove the button.

The trigger does not match what you did

Check. Open Settings on the workflow, and read When should it run? The choices are A record is created, A record is updated, Created or updated, A record is deleted, Adhoc and From a webhook. Also check the module: a workflow runs only for records of the module it belongs to.

Fix. Pick the trigger that matches. Typical slips:

• You edited a record but the workflow runs on A record is created.
• You want a check before the save. For Before the save, can stop it (PRE), choose the exact event: one workflow for A record is created and one for A record is updated.
• You want the workflow to run only for some records. Put the condition in a Decision as the first step.
• You want a daily run. Build it as its own Adhoc workflow with Also run on a schedule on, and let it Load data for itself, because a scheduled run has no starting record. Keep record-triggered work in a separate workflow.

A before-the-save workflow stopped the save

Check. If the record was never saved, the after-save workflows never started. Look at the message the person saw when they pressed Save. A Before the save, can stop it (PRE) workflow that ends with Terminate set to Failed, or that fails a step, blocks the save and shows its message.

Fix. Read the message, then open the PRE workflow’s Runs. A failed PRE run is normal when a rule worked as designed. A clean ending lets the save through. See Before the save or after: PRE and POST workflows.

Another workflow’s change did not start it

Check. A Record manager step saves like any other save, so it starts the workflows of the module it writes to. The automatic changes of an Approval task, such as Set a stage on the record, are meant to label the record.

Fix. When another workflow must react to an approval, put a Record manager step on the Approved or Rejected path to make the change.

Watch out

A workflow that updates its own module can start itself again. Gate it with a Decision as the first step, so it ends when there is nothing to do.

The first Decision ended it quietly

Check. Open the run. If it shows Completed with a few steps and no changes, a Decision may have sent the record down a path that has no step after it. The workflow ends there, successfully.

Fix. Add the steps you meant on the Yes and No paths, or adjust the condition. Test it with a record whose values you know.

You called the webhook and nothing happened

Check. The webhook answers at once. Read the reply.

Reply	Meaning
202 and ACCEPTED	Beezr took the call. The run starts a moment later
400	The address is wrong, or the workflow is off
401	Require an API key is on, and the api-key header is missing or wrong
413	The payload is too large
503	Beezr could not store the call. Try again

Fix. Use the address from Copy webhook URL, send JSON, and send the api-key header if the switch is on. A 202 confirms receipt. Open Runs and find the run ID from the reply to check the outcome. If the payload is missing a field, the JSON parser step fails, and the debugger shows which one.

The change is not saved yet

Check. In the designer, the status next to the name should read All changes saved, and Check should show a tick.

Fix. Connect every step to a path, click Check, fix what it lists, then Save.