Summary:

• When pipelines fail using a self-hosted runner in Bitbucket Cloud with an error message indicating "unable to fetch the step" and "system error," the error message should provide clear and actionable information. Additionally, include the runner UUID in the error message to help identify the specific runner, especially in environments using autoscalers.

Current Behavior:

• When a pipeline fails due to a system error on a self-hosted runner, users receive a generic error message stating "unable to fetch the step" and "system error." This message lacks specificity, making it difficult for users to diagnose and resolve the issue. Furthermore, in environments leveraging autoscaling, identifying the specific runner instance that encountered the issue is challenging without the runner UUID.

Proposed Improvement:

Enhanced Error Messaging:

• Provide detailed error messages that specify the root cause of the failure. For example, if the issue is related to network connectivity, authentication, or resource availability, clearly indicate this in the error message.

Inclusion of Runner UUID:

• Include the UUID of the self-hosted runner in the error message. This will assist users in quickly identifying the affected runner and check the runner logs, particularly in environments where autoscalers dynamically manage runner instances.