Skip to main content

Common automation errors

Learn what the common errors of a failed automation run mean and how to fix them, from missing required fields to permissions, limits, and blocked requests.

Written by Leo

Tip: Find the error first. If an automation fails, Tape logs it as a failed run. Open the automation, click ▷ next to Manual run, then select the run. It lists every step, and the failed step shows its error message. Learn more about Automation runs →

The runs sidebar of an automation opens with the run button next to Manual run. The failed run is expanded, and the failed Create a record step shows its error message.

A required value is missing

A step can't save a record or comment because something it needs is empty. For example, Create record needs a value for a required field, or Add comment has no text.

A failed run in the runs sidebar. The Create a record step is marked Failed and its log reads Missing values for required fields: What problem.

How to fix it

Open the failed step and fill in every required field of the database app. If the value comes from a record value, check that the field isn't empty on the record that started the run. For example, if Create record needs a Vendor and the expense has none, set a fallback value or add a conditional step that checks the field first.

You don't have permission

The automation tried to do something that the person behind it isn't allowed to do. This also happens when a custom author is set on a step and that author doesn't have enough permissions.

How to fix it

Open the step, select its •••, then select Author. Choose a person who can access the database app and the records involved, or give the current author the missing access. The author needs permission to create or edit records in the database, the same as when they do it by hand. Learn more about Action settings →

The ••• menu of the Update the current record action with Settings, Author, Silent, Trigger automations, Trigger webhooks, Continue on error, Deactivate, Turn into, Duplicate, and Remove
Selecting ••• on the Update the current record action, opening the Author dropdown, and choosing Juliet Adams from the members, so Author shows Juliet Adams

A person, field, or app can't be found

A step uses something that was deleted or removed, for example a deleted field or an app that's gone.

Deactivated members don't cause this error. An automation can still use them: the run succeeds, sets the person field, and shows the deactivated member as the author of the change.

How to fix it

  1. Open the failed step.

  2. Check the people, fields, and apps it uses, including values in person fields on the record.

  3. Select a person or field that exists, then select Save changes.

A date or value has the wrong format

A step receives a value of the wrong kind, for example text in a number field, or a date that isn't written as YYYY-MM-DD HH:mm:ss. Dates you build in a script must match the format of Tape dates: 2026-02-01 15:00:00 for a date with time, 2026-02-01 for a date, and 15:00:00 for a time.

How to fix it

Check the value the step receives. Use Manual run on a test record to see the value the step receives. In a script, write the date in the format above. If the date shifts by hours, the cause is the time zone. Learn more about Dates or times are off →

A field with several values gets the wrong kind of value

A step gives a person, category, or relation field a value that doesn't fit the field, for example plain text from a script or a webhook instead of a person or a record. The step then fails with an error.

How to fix it

Make sure the value matches the field: one option for a single-select field, a list of people or records for a field that holds several. For fields with several values, choose how the step applies the value, for example Set people, Add people, Remove people, or Clear people. Set replaces the current values, Add adds to them, Remove takes values out, and Clear empties the field.

The run took too long

A single run can take at most three minutes. Longer runs fail with the message "Action execution failed due to timeout. Avoid long runtimes for your workflow."

How to fix it

Split the work into several automations. A big job can call another automation for each batch, or run on a schedule and process a limited number of records at a time. Learn more about Limits and throttling →

The run used too many actions

A single run can use at most 1,000 actions. A loop repeats its steps for every record, so it can use many actions.

How to fix it

Reduce what the loop touches. Filter the records first, process fewer records per run, or split the job into batches. Learn more about Update many records in batches →

The run ran out of memory or processing time

Memory and processing limits apply to every run. Heavy calculations and large lists can use them up, and the run fails with an error message.

How to fix it

Avoid heavy calculations on large amounts of records. Search for fewer records, and process them in smaller batches.

Not all records were found

A single Search for records step returns at most 1,000 records. If a search matches more, Tape cuts the list to 1,000 without an error, so the run still shows Success.

How to fix it

Narrow the search with filters, or work through the records in batches, for example on a schedule. Learn more about Collected records →

A script threw an error

If an Execute script or Perform calculation step throws an error, the run fails and logs that message. Stopping on purpose this way is also a clean way to end a run when a key step fails, because the remaining steps don't run.

How to fix it

Read the message in the failed step. Use console.info in the script to log values. The logs appear in the runs sidebar. Learn more about Execute script →

An HTTP request is blocked or fails

Send HTTP request and Send API request only call services that are reachable on the public internet. A request to a private, internal, or local address is refused. If the other service takes too long to answer, the run can reach its time limit of three minutes.

How to fix it

  • Use a public address for the service.

  • If the service only accepts known addresses, add the IP addresses of Tape's automation servers to its allow list. These addresses can change, so avoid relying on them if you can. Learn more about IP addresses →

  • If the service is slow, check that it's available and send smaller requests.

An email wasn't sent

Emails sent through Tape's own sending account share your organization's quota for 24 hours. Once it's used up, the Send an email step fails with an error, and the run fails unless the step has Continue on error turned on. Emails you send through your own email account don't count toward this quota.

How to fix it

Wait until the window rolls over. To use fewer emails, send one summary email instead of one email per record. Learn more about My automation emails don't arrive →

The run keeps going when a step fails

By default, a failed step stops the run. If you want the run to continue, select the ••• of the step, then select Continue on error. If nothing else fails, the run then ends as Success. The failed step still shows its error, and the error is saved in the variable Most recent error. Learn more about Error handling →

Selecting ••• on the Update the current record action and turning on Continue on error

Tip: Still having trouble? Ask in the Tape community and include the automation name and the date of the failed run.

Learn more

FAQs

Can I get notified when a run fails?

Yes! Open the automation, click ▷ next to Manual run, then select Follow. The tooltip reads "Receive notifications for all failed runs".

Why did the run succeed but not do everything?

If a run shows Success but some records are missing, it could be because:

  • A search returned its maximum of 1,000 records.

  • A filter or condition skipped the step.

  • A step is set to Continue on error, so a failure didn't stop the run.

Can I try a fix without changing my data?

A simulated run goes through the actions without changing your data, but it skips the filter, so the filter step shows Skipped. To test a fix to a filter, use Manual run on a test record.

Why does the same error appear only for some records?

Values come from the record that started the run. If a field is empty or holds an unexpected value on one record, a step that needs it fails for that record only.

Still have questions? Find answers and get help from community experts in the Tape community →

Did this answer your question?