Pipeline build failed with "Step exceeded processing limits and has timed out" error

Summary

Pipeline build failed with "Step exceeded processing limits and has timed out" error

This is a generic scenario

Solution

Possible causes:

• The maximum length of all combined pipeline variables' names and values has been exceeded, the current limit is 120k.

Troubleshooting Steps:

Get the Repository, Workspace, and Deployment Variables and their values. Combine all the variable names and values together and verify the concatenated data length. Is the combined size of variable names and values more than 120k characters combined?

YES

• Currently, when a build has multiple variables configured (including Repository, Workspace, and Deployment Variables) and has more than a total of 120k characters combined, it could cause the pipeline build to be in a stalled state or fail with the above error message.

• To fix the issue, reduce the size of the variables to keep them under a total of 120k characters combined.

• Note, BCLOUD-20105 tracks a feature request to provide an informative error in the UI for such cases.

NO

• Raise a Support Ticket and share the Pipeline build URL from bitbucket.org