Error handling is how you control what an automation does when something goes wrong (an action fails, a value is missing, or a limit is reached). It's meant to help you find problems quickly and keep a single failed step from blocking work that doesn't depend on it.
You can use error handling for many things, including:
Letting an email step fail quietly while the rest of an onboarding automation still runs.
Stopping a run on purpose when a lead has no email address, so the problem shows up in your runs.
Note:
A failed action stops the run by default. The run gets the status
Failed, and the actions after the failed step don't run. You can change this per action withContinue on error.There are no automatic retries for actions and no separate error flow. Automations don't run an action again on their own, and you can't attach a second set of actions that starts only when something fails. The patterns below are workarounds. If a mail server turns an email away, Tape may try to deliver it again a few times in the background.
Find out what failed
Every run is logged, whether it started from a trigger, a manual run, or a simulated run. A failed run keeps the log of every step, including the failed action and its error message.
To see why a run failed:
Open the database app and click the automations icon in the top bar (tooltip
Create and view automations), then open the automation. The icon is only there for workspace admins, and not on mobile.Click
▷next toManual run(View all runs) to open theRunspanel.Select the failed run to open its steps and read the message on the failed step.
Select Follow at the top of the Runs panel to receive notifications for all failed runs of that automation. They appear in your notifications in Tape and as push notifications on your phone. Tape doesn't send them by email. Workspace admins can follow an automation. The person who creates an automation follows it automatically.
If you're an organization owner or admin, you can also get failures in another tool. Open Runs in the Automation Center, select the settings menu (Webhook, export and more), then Webhook notifications. Select Add webhook. The webhook appears in the list right away. Then enter the URL and choose Run failed, Action failed, or Organization throttled.
Tip: You can also review failures for all automations at once in the Automation Center. Learn more about the Automation Center →
Continue past a failed action
Every action has a menu with Continue on error. When you turn it on, the run goes on with the next action even if this one fails.
To let a run continue after an action fails:
Hover over the action and click
•••.Select
Continue on error.Select
Save changes.
Use it for steps that are nice to have but not required, such as a notification email. Don't use it for steps that later actions depend on, like creating a record that you update in the next step.
The run is marked as
Success, as long as nothing else fails. The failed step still shows its error.Later actions can react to the error. Tape saves the error in the variable
Most recent error. AddConditional actionsafter the step. Click•••next to its filter and selectTurn into script filter, then checkMost recent errorin the script.
To skip a step without deleting it, click ••• on the action and turn on Deactivate. Tape skips the step in every run.
Check values before you act
Many failures come from missing or unexpected values, for example an empty email field. With Conditional actions, you can check the value first and handle the problem on purpose.
For example, to avoid a failed email step:
Select
Add action→Conditional actions.Select
Add filterand set the conditionEmailIs not empty.Add
Send emailinside the block.Open the block's menu
•••and selectElse statement. Inside it, add the actions that handle the problem.
The Else statement branch runs when the conditions aren't met. Use it to create a record in a log database app, add a comment to the record, or end the run with a status.
End a run on purpose
Select Add action → End run to stop the run at that point. Actions below it don't run. The status is either Success or Failed.
Successends the run and marks it as completed.Failedends the run and marks it as failed.
The run shows the status you chose. With Failed, the End run step is marked as failed.
Put End run with Failed inside the Else statement of a check, and the run list shows every record that didn't pass.
Fail a run from a script
In Execute script, you can stop a run with a custom message by throwing an error. The run fails at that point, the message is logged, and the remaining actions don't run.
if (!lead_field_email_email) {
throw new Error('Lead has no email address');
}lead_field_email_email stands for the email addresses in the Email field of a lead. The variable name depends on your database app and field. Type @ in the script to insert the right one.
Keep a log of problems
If you want a list of every record that needed attention, log it in a database app of its own:
Create a database app, for example
Automation log, with fields for the record, the reason, and the date.In the
Else statementof your check, selectAdd action→Create recordand fill in the log record.Add
End runwithFailedbelow it, so the run is also marked.
This logs problems that your own checks find. To also log errors that Tape or another service raises in an action, turn on Continue on error for that action. Then add Conditional actions with a script filter that checks Most recent error, and create the log record inside.
Run again after a failure
Automations don't retry, and a failed run can't be restarted from the run itself. After you fix the cause, you can run the automation again for the records that were affected: select Manual run, choose the records under Run on, then select Start run, or Save and start run if you have unsaved changes. Use Simulated run first if you want to see the result without changing data.
Limits that fail a run
A run fails with an error message when it goes over one of these limits:
A run can take up to three minutes.
A run can use up to 1,000 actions.
Memory and CPU limits apply.
To stay inside the limits, split big jobs into several automations or process records in batches. Learn more about limits and throttling →
One limit doesn't fail the run: a single collect action returns at most 1,000 records and cuts off the rest without an error. The email quota is different. Once your organization's 24-hour quota for emails sent through Tape's account is used up, the Send email step fails with an error, and the run fails unless the step has Continue on error turned on.
Common causes of errors
A required value is missing, for example a required field in
Create record. The step fails with a validation message.The author of an action doesn't have permission to do what the action asks. To set the author, click
•••on the action, then selectAuthor. If no author is set, the change is made by the automation.A script has a syntax error. Tape lets you save a script with an error, so the run fails.
Learn more
FAQs
Can I retry an action that failed?
Can I retry an action that failed?
No. Automations don't retry on their own, and you can't restart a failed run from the run itself. Fix the cause, then use Manual run on the affected records.
Can I run different actions when something fails?
Can I run different actions when something fails?
Yes, turn on Continue on error for the action, then add Conditional actions with a script filter that checks Most recent error. You can also check values yourself before an action and use the Else statement branch for the problem case. At this time, there's no separate failure branch.
What does Continue on error do?
What does Continue on error do?
With Continue on error turned on, the run goes on with the next action even if this action fails. The failure is still logged on that step, and the error is saved in the variable Most recent error. The run ends as Success, as long as nothing else fails.
How do I get notified when a run fails?
How do I get notified when a run fails?
Open the automation, then select Follow in the Runs panel. Tape notifies you about all failed runs of that automation, in Tape and as push notifications on your phone.
Why does my run fail even though every action looks fine?
Why does my run fail even though every action looks fine?
It may have hit a limit. If the run shows Workflow timeout, it took longer than three minutes. Workflow resource limit exceeded means it used too much memory or computing time. A run also fails when it uses more than 1,000 actions. Split the work into several automations, or process fewer records per run.
Are you a developer using the Tape API for automations?
Are you a developer using the Tape API for automations?
The automation API has its own documentation for developers. Full reference: exit in the developer docs →
Still have questions? Find answers and get help from community experts in the Tape community →
