Deploy notifications by email and Slack
Voroa emails you when a build fails, a new version will not start, or a service keeps restarting. What each email says, who gets it, and how to turn alerts off.
What this covers
A notification tells you something went wrong without you having to be looking. That matters most for the deploys nobody is watching, such as an automatic deploy triggered by a teammate’s push late in the day, where the gap between the failure and someone noticing can be hours.
Voroa sends these emails automatically. There is nothing to switch on.
The three emails Voroa sends
Build failed. Your build did not complete, so the new version was never deployed. The email names the service, shows the last lines of its build log, which is usually where the error is, and links to the full log.
Deploy failed. The build finished, but the service did not start. This is a different failure from the one above and it is worth knowing which you had: the code was built, so the problem is usually the start command, a missing environment variable, or something the service needs at run time that is not there. The email shows what your service printed before it stopped, so you can often see the fix without opening the dashboard.
Your service keeps restarting. A service started, stopped, and was started again, over and over. This one is not about a deploy at all - it can begin hours or days after a deploy that went perfectly. It normally means the start command is not right, something the code needs is not installed, or the program finishes its work instead of staying running.
Each email links straight to the service, so the person reading it on a phone can tell in a few seconds whether it needs them right now.
What happens to the version that was already running
A failed build does not take your site down. The version that was already running keeps running and keeps serving your users, and the failed build simply never replaces it. The emails say this, because it is the first thing most people want to know.
The exception is your first deploy. If it fails, there is no earlier version to fall back to, so the service is not live yet and its web address will not answer until a deploy succeeds. The email says that too.
Who receives them
The account owner. If your workspace has a separate billing email set, that address is included as well.
You cannot currently choose different recipients.
Turn alert emails on or off
Open Settings and choose Notifications. Two alerts have a switch, and both are on for a new workspace:
- Failed deploys - the build failed and deploy failed emails above.
- High memory or CPU - a service has stayed close to its memory or CPU limit. This one goes to the account owner only.
Only members who can change workspace settings can use the switches. While an alert is off it is still recorded, but no email is sent, and turning it back on does not send the ones you missed.
Everything else is always sent, because it tells you about something that changes your service or account: the restarting email above, disk and database storage warnings, payment and invoice emails, sign-in and security emails, and workspace invitations.
What is not available yet
Slack, Discord and webhook notifications are not available on Voroa today. Deploy results are also always shown in the dashboard against each service, whether or not you read the email.