Account Notifications — VibeView Docs

Where to find account notifications for your organization — credit grants, bonus streaming minutes, and other account updates — and how unread badges work.

The Notifications page shows account notifications for your organization — for example, when the VibeView team adds usage credit or bonus streaming minutes to your account. Open it from Notifications in the left sidebar.

Unread badge

When your organization receives a new notification, a badge appears on the Notifications item in the sidebar with the number of unread notifications. Read state is personal: each member of your organization sees their own unread badge until they open the notification.

Reading notifications

Each notification shows what happened (for example, “You’ve been granted $5.00 usage credit”), an optional message from the VibeView team, and when it happened. Unread notifications are marked with a coloured dot and sit at full contrast; ones you have already read fade back so the new ones stand out. Click an unread notification to mark it as read, or use Mark all as read to clear the badge in one step. The page header shows how many are still unread.

Notifications about credit apply to your organization’s shared balance — see AI Credits for how usage credit works.

Failed runs

When a run you started fails, you get a notification with a link to the run. Whether you also get an email depends on how you started it:

From the Run dialog (a test, a selection, a group or all tests, on one or more devices): a notification and an email, one for the whole run however many devices and tests it had.
From a coding agent with run_test or run_group and no session_id (the run starts its own devices), or from the API with POST /api/v1/tests/runs and your own token: the same, a notification and an email.
On a device you already have open: a run from the Run a test tab on the Devices page, or from a coding agent with a session_id, only shows in Notifications, because you are watching it.
From the CLI on your computer (vibeview run-test, run-suite): only shows in Notifications.
From a schedule: its owner gets a notification and an email.
From CI: no notification and no email. A CI run reports through GitHub, Slack and webhooks instead, including a CLI run in a CI job.

The notice names the first failed test and why. Only the person who started the run gets it; others in your organization don’t.

A run that couldn’t finish for a reason that isn’t your app, a cancelled run and a quarantined test’s failure don’t notify.

Explore

When an Explore run ends, the person who started it gets a notification and an email with a link to the run, since an Explore run takes 5 to 20 minutes and you may have walked away. The title says how it went: Explore finished with the number of findings (or “no findings”), or Explore stopped with the reason when it ended early, for example when usage credit ran out or the AI service didn’t answer. A run you cancel doesn’t notify, and neither does one started from CI. Others in your organization don’t get it.

Scheduled runs

A schedule also tells you when it needs you:

Schedule paused: when its owner can no longer run it, everyone in your organization gets this notification, without email. For the other reasons (a move to the Free plan, something it runs was deleted, three runs in a row that couldn’t start), its owner gets it, in-app and by email.
Schedule changed: when an app is removed from a product and a schedule loses that app’s devices but keeps others, its owner gets it, in-app and by email, naming the devices it lost. The schedule keeps running on the rest.
Scheduled run didn’t start: the first time a run couldn’t start (for example, no usage credit left), its owner gets it, in-app and by email. Its owner also gets it when a run started but none of its devices ran its tests, for example because no device became free within the run’s time limit.
Part of a scheduled run didn’t run: some of a run’s devices didn’t run its tests (for example, no device became free within the run’s time limit), while the others did. Its owner gets it, in-app and by email, with how many devices didn’t run and why.
Scheduled run stopped: a run that went past its time limit was cancelled. Its owner gets it, in-app and by email.

Click the notification to open the schedules (or the run).