Console option to retry a failed Terraform Module test run
Would like an option to retry a failed module test by clicking a “retry” button in the console.
I’m not actually sure how to retry a module pipeline, other than amending the commit and force-pushing, or creating a new commit. But that will run all tests, instead of only the failed one.
- Workaround
- No
Log in to comment and vote
Comments5
Natalia Gazda
Aug 28, 2025
Hey @Loren Gordon @Aleksandar Andonov we added a button to retry failed tests on PRs, but we don't allow retrying tests on versions. Does it solve your problem with the current approach?
Yellow Mirror
Aug 28, 2025
I see the retry button on a failed module test for a PR, and that should work. But what is the rationale for preventing retries on a failed version? We definitely have situations in that case where a retry is appropriate, and retrying the entire version means re-running test cases that already passed…
Bronze Skateboard
Nov 19, 2024
We are facing a similar problem.
A pull request in the repository hosting a terraform module triggers a proposed run (via a push policy). This runs the tests associated with the changes and verifies the PR. The result is written back to the repository system (Azure DevOps) as a status check.
However, if a test fails (due to side effects in the testing environment, e.g., failed clean-up from previous test runs, etc.), it is not possible to run the test again and get a positive status check back in Azure DevOps. Raising a new PR does not alleviate the problem. Adding new commits in the PR does solve it, but is not a suitable workaround in our scenario.
A button to manually retry the failing tests in this situation would be very helpful and enable our workflow to deal with such situations gracefully.
Natalia Gazda
Nov 19, 2024
Thanks for the feedback Aleksandar! We looked at it, and we understand the problem. However it’s a major effort from our side, so I would ask you for a bit of patience ad it’s not something we can do right away.
Yellow Mirror
Nov 7, 2024
This applies to both module PRs and Versions. There is currently an option to retry a failed tracked run for the module version, but that will run all tests, instead of just a failed one.