FastStore WebOps now includes a rerun feature for failed builds. This allows you to directly execute a failed build from the dashboard.

With this feature, you can quickly resolve issues that are not related to code, such as misconfigurations of environment variables or network interruptions, without having to create a new commit in your repository.

Previously, if a build failed due to non-code issues, you had to make a new commit to the repository to trigger a rebuild.

Now, you can rerun the build job from the WebOps interface itself, enabling you to resolve operational problems more quickly without modifying your codebase or affecting your commit history.

This feature is available for all WebOps users, and no additional configuration is required. To use it, follow the instructions below:

1. In the Deploys tab of FastStore WebOps, click the entry you want to redeploy.
2. In the top-right corner of the page, click ⋮, then click Rerun this deployment.

If the build failed due to problems in your code (for example, syntax errors or failing tests), update the code in your local environment and push a new commit. WebOps will automatically trigger a new deploy for that commit.