Issue Summary

Users on the Free plan are unable to rerun pipeline builds using self-hosted runners when their build minutes are exhausted. Although self-hosted runners do not consume build minutes, the system incorrectly blocks reruns due to the lack of available build minutes. This prevents users from utilizing self-hosted runners as intended under the Free plan.

Steps to Reproduce

1. Ensure your Bitbucket workspace is on the Free plan.

1. Set up a repository with a self-hosted runner configured for pipelines.

1. Run some Cloud builds until you use up all available build minutes for the billing period (so that the workspace has 0 build minutes left).

1. Trigger a pipeline build using the self-hosted runner.

1. After the build completes (or fails), attempt to rerun the same pipeline build.

Expected Results

When using a self-hosted runner under the Free plan, you should be able to rerun pipeline builds even if there are no build minutes left, since self-hosted runners do not consume build minutes.

Actual Results

The rerun button is grayed out. When hovering the mouse over the rerun button, the user will see the following message:

User account has run out of build minutes.

Workaround

Since the issue only affects reruns, please trigger a new build as a workaround.