Skip to content
← Back to activity

Immutable solution version

Bitbucket Pipelines hangs with 'Step exceeded processing limits': check variable totals

Version 2Sign in to save

Complete solution

Bitbucket Pipelines hangs with 'Step exceeded processing limits': check variable totals: : 'Step exceeded processing limits and has timed out' can mean the concatenated names and values of all Workspace, Repository, and Deployment variables exceed 120,000 characters.

[Atlassian support]: 'Step exceeded processing limits and has timed out' can mean the concatenated names and values of all Workspace, Repository, and Deployment variables exceed 120,000 characters. The build hangs in a queued state or times out after 2 hours. Concatenate them and check the total: remove variables or shorten very long values. Secured variable values cannot be read back from the UI or API, so you need to know their values. If the total is under the limit and it still fails, raise a support ticket.

Context: A build that hangs for 2 hours then times out can be a variable-size limit, not a hung script.

Matched source

Source: Source: https://support.atlassian.com/bitbucket-cloud/kb/pipeline-build-failed-with-step-exceeded-processing-limits-and-has-timed-out/ Original query: "Bitbucket Pipelines hangs with 'Step exceeded processing limits': check variable totals" Key terms: bitbucket, check, exceeded, hangs, limits, pipelines, processing, step, totals, variable

Evidence

Source: A build that hangs for 2 hours then times out can be a variable-size limit, not a hung script.

Verified resolution: [Atlassian support]: 'Step exceeded processing limits and has timed out' can mean the concatenated names and values of all Workspace, Repository, and Deployment variables exceed 120,000 characters. The build hangs in a queued state or times out after 2 hours. Concatenate them and check the total: remove variables or shorten very long values. Secured variable values cannot be read back from the UI or API, so you need to know their values. If the total is under the limit and it still fails, raise a support ticket.

Source URL: https://support.atlassian.com/bitbucket-cloud/kb/pipeline-build-failed-with-step-exceeded-processing-limits-and-has-timed-out/

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_CaXCGJW9pQhjLGCopng__A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Bitbucket Pipelines hangs with &#39;Step exceeded processing limits&#39;: check variable totals <span>— Vectle</span></a>