# Fix a workflow that does not run as expected

> Find out why a workflow did not start, skipped a step or failed, what each error means, and which limits and plan settings apply to workflows.

Source: https://tadabase.com/docs/workflows/workflow-limits-and-troubleshooting  
Status: Verified Nov 17, 2026. Checked against the current product

Most workflow problems are one of three things: the workflow never started, it started but a step was skipped, or a step failed. Start in the workflow's **History**, then use the tables below to match what you see to its cause.

## Start here

1. **Open the history** In the workflow editor, click **History**. See [Check workflow runs, history and errors](https://tadabase.com/docs/workflows/workflow-history-and-logs).
2. **Look for the run** Set the date filter to the time you expected the run. No run at all means the workflow did not start: see the next section.
3. **Open the run** Click **Details**, select the record, and read the first step marked as failed or skipped. **Rules checked** shows why a condition did not match; **This step failed** shows the error, why it happened and what to do.

## The workflow did not run

| What you see | Cause | Fix |
| --- | --- | --- |
| No run in History | The workflow is **Inactive**. | Turn the switch at the top of the editor to **Active** and save. |
| No run after you edited a record | The trigger is **Record Created**, which does not run on edits. | Use **Record Updated**, or **Record Created or Updated**. |
| No run after another workflow changed the record | A workflow's own changes never start that same workflow again, and a workflow that already ran for a change is not run a second time for it. Tadabase also stops a chain of workflows that start each other after five in a row. | Do the work in the first workflow, or start the other workflow from a step instead of relying on the record change. |
| A scheduled run shows as **Skipped** | The previous run of the same schedule was still running, or the run was picked up more than 30 minutes after its time. | Make each run shorter, for example with filters under **Record Selection**, or schedule it less often. |
| A scheduled run has 0 records | No record matched the filters under **Record Selection**. | Open the trigger and check the filters and **Limit**. |
| Every run shows as **Skipped** | The workflow has no steps. | Add at least one step. |
| **Hourly** or **Every Minute** is missing from the schedule menu | Your plan does not include that schedule. | Choose **Daily** or longer, or change plan. |

## It ran, but a step was skipped

| What you see | Cause | Fix |
| --- | --- | --- |
| **This step did not run.** | The step's **Enabled** switch on its **Advanced** tab is off, or the step sits on a path that was not taken. | Turn **Enabled** on, or check the condition or branch above the step. |
| **Condition not met** | A value on the record was not what the condition expected. **Rules checked** lists each rule with the **Value found**. | Compare **Value found** with the rule. A common cause is a field that was empty when the run started. See [Conditions and branches](https://tadabase.com/docs/workflows/conditions-and-branches). |
| Find Records is skipped with `No records matched the lookup filters.` | Nothing matched the step's filters. | Check the filters. See [Find records and use them in later steps](https://tadabase.com/docs/workflows/find-records-in-a-workflow). |
| Steps marked as simulated | The run was a **Dry run**. | Use **Run** instead of **Dry run** to make real changes. |

## A step failed

A failed step shows its error in plain words, why it happened and what to do. The most common ones:

| Error | What it means | What to do |
| --- | --- | --- |
| This email had no one to send to. | The **To** address was empty when the step ran. | Add a recipient, or make sure the field it uses has an email address. |
| The email was blocked and not sent. | The app's sender email is not verified, a trial reached its email limit, or email is blocked for the account. | Verify the sender email in the app's email settings, or contact Support. |
| The other service did not answer. | The service a webhook or code step calls was offline or refused the connection. | Check the service, then rerun. |
| The other service asked us to slow down. | Too many requests in a short time. | Wait a few minutes, or run the workflow less often. |
| The other service refused our sign-in. | The saved key or password is wrong, expired or lacks permission. | Update it, for example in **App Secrets**, then rerun. |
| This step took too long and was stopped. | The step did not finish in the time one run is allowed. | Have it handle fewer records, for example with a filter. |
| This run was too large to finish. | More data than one run can hold. | Process fewer records per run. |
| A required field was left empty. | The step saved a record without a value a field needs. | Make sure the field always gets a value. |
| A record like this already exists. | A value that must be unique matched an existing record. | Change the value, or update the existing record instead. |
| This step points at a field that no longer exists. | A field the step uses was renamed or deleted. | Open the step, pick the field again and save. |
| Something went wrong on our side while running this step. | Not caused by your settings. | Rerun. If it happens again, contact Support with the run ID. |

After a failed step the run carries on with the next step. To stop the run there instead, turn on **Abort workflow if this step fails** on the step's **Advanced** tab. When you have fixed the cause, open the run and use **Rerun** to run only the failed records again.

## Built-in limits

| Limit | What happens |
| --- | --- |
| Steps in one workflow: 100, unless your plan sets a different number | A run of a workflow with more steps fails at the start with `WF_MAX_STEPS`. |
| Steps nested inside conditions, branches and loops: 10 levels | A deeper workflow fails at the start with `WF_MAX_DEPTH`. |
| Workflows that start each other through record changes: 5 in a row | The next workflow in the chain is not started. |
| A loop inside a loop | Not possible. **Loop / Bulk Action** is not offered inside another loop. |
| **Find Records**: 1 to 500 records per step | **Count all matches** counts up to 10,000. |
| **Run Custom Code**: 30 seconds per run of the code | The step stops with a time-out error. |
| Time for a whole run | A run that goes past it is stopped and shown as failed. |
| Temporary problems on Tadabase's side | The run is started again automatically, up to three attempts in total. |
| Scheduled runs | Never overlap: a run that is due while the previous one is still going is skipped. |

## Plan limits

|  | Business Starter | Business Growth | Business Pro | Business Elite |
| --- | --- | --- | --- | --- |
| Workflows | 15 | 40 | 100 | 200 |

- When you reach your plan's number of workflows, **New Workflow** is replaced by an upgrade button.
- **Hourly** and **Every Minute** schedules are plan features. Saving a workflow with one your plan lacks shows `Your plan doesn't allow workflows to run hourly.` (or `every minute`).
- The **Incoming Webhook** trigger is on Business Growth, Pro and Elite.
- **Versions**, **AI Prompt** steps and PDF steps also depend on your plan. If an option is missing from the editor, your plan does not include it.

## When to contact Support

If History does not explain what happened, contact Support with:

- The app and workflow name.
- The run ID: open the run and click the ID under **Run** to copy it.
- What you expected to happen and what happened instead.
- The error shown on the failed step.
