JavaScript was terminated after 90 sec. timeout

If a JavaScript runs longer, the workflow is automatically stopped with the following error:

The Workflow finished with the result: Javascript was terminated after 90 sec. timeout (Javascript running longer than 90 sec. is not supported).

When this happens

This usually occurs when a workflow processes too much data or performs too many operations in a single run, for example:

• looping through large datasets,
• running repeated lookups or calculations,
• creating or updating many records,
• generating large reports.

Does it depend on where the script runs?

Yes. This limit applies only to server-side workflows.

Common causes

The issue is often caused not only by data volume, but also by inefficient script design, such as:

• repeated getData() calls inside loops,
• loading unnecessary fields,
• creating or updating records one by one instead of in bulk,
• combining too much processing into a single workflow run.

How to prevent it

To reduce the risk of hitting the limit:

• use bulk operations such as createRecordsBulk or updateRecordsBulk,
• use loadFields to load only required fields,
• limit the number of processed records,
• minimize repeated queries,
• split large reports or heavy processing into smaller steps.

Recommendation

If this error occurs repeatedly, review the workflow with focus on:

• how much data is loaded,
• how many operations run inside loops,
• whether bulk operations can be used,
• whether the process can be divided into smaller parts.