.svg?fit=max&auto=format&n=mBaWmVpTOpDBIB6_&q=85&s=36c7989ebe591de9ac7d3618f0a04a28)
.svg?fit=max&auto=format&n=mBaWmVpTOpDBIB6_&q=85&s=5afe473ba3ef2469d3e839045bcb099c)
What triggers a notification
Meridian creates a notification the moment a deployment’s status changes to Failed. Exactly one notification is created per failed deployment, no matter how many times the failure is observed or retried. Each notification carries the app and environment name, the failure reason, and the pipeline step it failed at, for example:
See Deployment for what each step means and Logs for the full build and runtime output behind the failure.
Opening a notification
Click the bell to open the panel, which lists your organization’s most recent notifications, unread ones highlighted first. Clicking a notification marks it read and takes you straight to the Hosting page for that app, with the failed deployment and its environment already selected so you land on the right log rather than having to hunt for it. Use Mark all read to clear the unread badge for every notification currently visible to you.Who sees what
Read state is per user: one teammate clearing their unread badge doesn’t affect anyone else’s. Which notifications you see depends on your app access within the organization:- Owners, and members with a role scoped to all apps, see every failure across the organization.
- Collaborators restricted to specific apps only see notifications for apps they can access. Deployment failures for apps outside their access never appear, even in the unread count.
Staying up to date
There’s no live push yet, so the panel refreshes on:- Bringing the browser tab back into focus, if the list is stale
- Seeing a new deployment failure elsewhere in the dashboard (for example, on the Hosting page)
- A safety-net check every 10 minutes