To fix a broken deployment, roll back to the last stable version, review deployment logs for errors, and ensure all configurations are correct.

When you encounter a broken deployment in your web app, the first step is to roll back to the last stable version. Most deployment platforms provide an option to revert to previous versions, ensuring minimal downtime for your users. Once you've restored a stable version, it’s crucial to examine the deployment logs. These logs contain detailed information about what happened during the deployment process, including any errors or warnings that may have occurred. Look for specific error messages that can point you in the right direction. Common issues include misconfigured environment variables, outdated dependencies, or missing files that weren't included in the deployment package. After identifying the errors, check your configuration settings. This includes verifying that your database connections are properly configured and that any required environment variables are correctly set. Additionally, ensure that your build scripts and asset compilation processes are functioning correctly. It may be helpful to test these scripts locally before redeploying. Finally, once you've addressed the issues, test the deployment in a staging environment if possible. This allows you to verify that everything is working as expected before going live again. With thorough investigation and careful correction of errors, you can successfully fix a broken deployment and prevent similar issues in the future.