Zapier Code Timeout (2026): Runtime Limits, 10-Minute Extended Runtime & Fixes

Current limits

Zapier Code by Zapier timeout limits in 2026

These are the current runtime figures documented by Zapier. The important distinction is between standard runtime and extended runtime.

Source: Zapier — Using Code by Zapier and Zapier — How Code by Zapier usage is measured .

The practical fix

Can you increase the Zapier Code timeout beyond 30 seconds?

Yes, but only for eligible Code action steps. On Professional, Team and Enterprise, Zapier’s extended-runtime feature allows a Code action to run for longer than its standard runtime, up to a maximum of 10 minutes.

The feature is configured from the Code editor. Zapier describes selectable extensions that increase the step’s maximum runtime. The maximum total runtime depends on the plan and the extension selected.

Source: Zapier — Configure extended runtimes for Code steps .

Cost matters

How Zapier’s extended runtime billing works

Extended runtime is not simply a free switch that removes the timeout. Zapier’s current usage documentation says each Code step run uses one task for initialization, while execution beyond the standard runtime adds one task for every additional 30 seconds. Partial 30-second blocks round up.

The implication is important: moving from 30 seconds to a longer runtime changes the cost model as well as the timeout behavior.

Source: Zapier — How is Code by Zapier usage measured? .

Diagnosis

Why does a correct Zapier Code step still time out?

A timeout message does not automatically mean the JavaScript has a bug. In production, the runtime can grow because the input grows, an external API slows down, a package takes longer to install, or the code performs more work than the test sample represented.

The limits around the timeout

Other Zapier Code limits people often confuse with a timeout

Sources: Code by Zapier , Troubleshooting Code , Code rate limits , and Looping by Zapier .

Troubleshooting playbook

What to do when your Zapier Code step times out

Start with the smallest change that addresses the actual failure. Moving platforms should be a choice, not the automatic response to the word “timeout.”

Rate limits

Current Code by Zapier rate limits

Rate limiting is different from runtime. A Code step can be fast enough to finish in milliseconds and still be affected by the account’s Code-step request limit.

Source: Zapier — Code by Zapier rate limits .

Looping

Is the 500-iteration Looping limit the same as the Code timeout?

No. They are different constraints.

Looping by Zapier is a separate step designed to repeat subsequent actions for each item. Zapier currently documents a maximum of 500 loop iterations. The loop iterations run in parallel, and each action after the loop can generate task usage for every iteration.

A JavaScript loop written inside a Code step is different. It is not limited to 500 iterations by the Looping feature, but the Code step is still constrained by its execution runtime, memory, rate limits and output restrictions.

Source: Zapier — Understanding Looping by Zapier .

Why search results are confusing

How Zapier’s Code runtime limits changed

Search results contain a mixture of historical and current Zapier documentation. That is one reason you can find three different “correct” answers to the same timeout question.

Current references: Zapier plan changes , 2025 runtime update , and 2026 extended runtimes .

Alternative execution model

Zapier vs Latenode: what actually changes?

Latenode is relevant when the issue is not simply “I forgot to enable extended runtime,” but that the workflow has become a longer-running piece of application logic.

Sources: Latenode — CPU seconds , Latenode — execution timeout , and Latenode — JavaScript .

Migration

Moving JavaScript from Zapier Code to Latenode

The algorithm can often be reused, but the wrapper and input mapping should normally be rewritten for the destination environment.

Typical Zapier Code pattern

const items = (inputData && inputData.items) ? inputData.items : [];

const total = items.reduce(
  (sum, item) => sum + Number((item && item.amount) ? item.amount : 0),
  0
);

return {
  count: items.length,
  total: total
};

Typical Latenode JavaScript node structure

export default async function run({ execution_id, input, data }) {
  const items = (input && input.items) ? input.items : [];

  const total = items.reduce(
    (sum, item) => sum + Number((item && item.amount) ? item.amount : 0),
    0
  );

  return {
    count: items.length,
    total: total
  };
}

The important part is not the syntax alone. In Latenode, values from previous nodes are mapped through its Data system, while Zapier Code actions use their own input-data and output conventions. Latenode also documents a different JavaScript module structure and npm package workflow.

Latenode JavaScript reference: JavaScript node documentation .

Architecture decision

When staying in Zapier makes sense

A longer runtime alone does not mean a workflow needs a new platform. Zapier’s current Code tooling also includes the Zapier SDK, allowing JavaScript Code steps to run actions and authenticated API requests using existing app connections.

For a small transformation, validation rule, calculation or API operation that reliably completes inside the available runtime, keeping it inside the existing Zap can reduce infrastructure and maintenance overhead.

The stronger reason to reconsider the architecture is a workload that repeatedly pushes against execution ceilings, requires more processing than the available runtime, needs extensive looping or becomes difficult to observe and maintain as application logic.

Primary documentation

Primary sources used for this guide

Product limits change. These are the first-party sources used for the figures and statements on this page, so readers can verify the current configuration directly.

Answers

Frequently asked questions about Zapier Code Timeout