Next Gen Zap limitations

Next Gen Zaps have limits on how much code a workflow holds, how long a run can wait, and how long Zapier keeps your data. Some features you use in Classic Zaps are not available in Next Gen Zaps yet. Check these limitations before you build a Next Gen Zap or import a Classic Zap.

Available on plans:

Free

Professional

Team

Enterprise

Early Access

Next Gen Zaps is in early access by request. Sign up at https://zapier.com/workflow/early-access. If you’re on a Team plan, the request must come from an account owner or admin. If you’re on an Enterprise plan, contact Support for access. This feature has limited availability and is in active development.

Workflow and run limits

• The TypeScript code of a Next Gen Zap has a 200,000-character limit.
• Each delay or wait for a callback in a run can last up to 1 year.
• If a run waits for a callback from another system and the callback does not arrive, the run keeps waiting. To start over, cancel the run and run the workflow again.
• Next Gen Zaps cannot limit a workflow to one run at a time. If a trigger fires several times close together, such as when you edit the same record quickly, each event starts its own run. These runs can overlap and repeat an action, such as sending the same email twice. Learn how to prevent duplicate data in Next Gen Zaps.
• Next Gen Zaps do not support Sub-Zaps. One Next Gen Zap cannot call another.
• Next Gen Zaps do not support Global, Zap, or System variables.
• The AI assistant in the Workflow Manager cannot read or return the URL of a published Zapier Forms page. To get the URL, go to your form in Zapier Forms and copy it from the Share dialog.

Sharing and editing

• You can only share viewer access to a Next Gen Zap. The people you share with can review the workflow but cannot edit it.
• Next Gen Zaps do not have an editor role yet. Only the workflow's owner, a super admin, or the account owner can edit a workflow, including through an AI tool.
  • To fix a workflow that you cannot edit, such as to replace an expired app connection, make your own copy. First, ask the workflow's owner, a super admin, or the account owner to turn off the original, so the two workflows do not both run. Then duplicate the original. You can duplicate any workflow that is shared with you, and you then own the copy. Connect your own app accounts in the copy, then turn it on.

Data retention and deletion

• You cannot restore a deleted Next Gen Zap yet.
• Zapier permanently deletes a Next Gen Zap 60 days after you delete it.
• Zapier keeps the run history of a Next Gen Zap for 60 days after each run finishes.
• Next Gen Zaps do not support custom data retention.
• Next Gen Zaps do not support self-serve data deletion or retention controls.
• Next Gen Zap data is not included when you export your Zapier account data with Export my data.

Features not supported yet

Some features are not supported in Next Gen Zaps during early access, and some are not yet confirmed to work the same way. Most of them are Enterprise features. For the full list, read the Enterprise customers section of Get started with Next Gen Zaps.

Limitations of specific tasks

Some limitations apply only while you do a specific task. They stay in the article for that task:

• Importing a Classic Zap: app connections that you cannot access, Zap variables, and Code by Zapier steps. Read Import a Classic Zap into a Next Gen Zap.
• Testing and publishing: the limit on test runs, and how publishing works from the Zapier SDK, the CLI, and MCP. Read Create Next Gen Zap drafts and versions.