Appearance
Notifications
Available now The bus emails your workspace when something needs a person:a rotated secret's overlap is ending, a connection is close to its daily allowance, one of your consumer queues is in trouble, a test run has finished, or a replay or redrive has finished. A house also hears when one of its vendors' connections goes silent or has too many messages refused. A vendor hears about its own connections in the houses it joined, from its own vendor workspace.
The checks run every 15 minutes, so an email can arrive up to about 15 minutes after the event.
What you can get
| When | Sent about | |
|---|---|---|
| Credentials | A client secret was rotated with an overlap, and the previous secret stops getting tokens within 6 hours (from an hour after the rotation: whoever rotated already knows). | Your workspace's own producer connections; in a vendor workspace, also your producer and consumer connections in houses |
| Daily allowance | A producer connection has used 80% or more of today's request allowance on the workspace routes (the day is UTC). | Your workspace's own producer connections; in a vendor workspace, also your producer connections in houses (each has its own allowance) |
| Consumer queues | A consumer connection's dead-letter queue has more messages than an hour ago, or the oldest message in its queue has waited longer than your lag threshold (15 minutes unless you change it). | Your workspace's own consumer connections that have a reader: a client secret, a verified reader role, or a reader RND set; in a vendor workspace, also your consumer connections in houses once you've got their client secret |
| Test runs | A test run finished: a skill harness run once its verdicts are in, a consumer run once you've reported its end state, or either run stopped with an error. The email gives the pass and fail counts and links to the run. A consumer run whose end state never came in (it expires after 24 hours) sends no email. | Test runs in your workspace |
| Replay and redrive | A replay from the archive, or a dead-letter queue redrive, finished, failed or was cancelled. The email gives the time range, or how many messages were moved. One the bus refused to start sends no email: whoever tried was told there and then. | Your workspace's own consumer connections |
| Refusals in houses (vendor workspaces only) | 25% or more of the messages one of your producer connections sent into a house in the last hour were refused, once it has sent 20 in that hour. The email names the rules that refused the most: they are your own results. | Your producer connections in the houses you joined |
| Vendor connections (houses only) | A vendor's producer connection that was sending has sent nothing for your chosen hours (12 unless you change it), and again when it sends; or 25% or more (your choice) of its messages in the last hour were refused, once it has sent 20 in that hour. Counts only: never which rules refused them. | Other organisations' producer connections in your house |
Client secrets don't expire on their own, so there's no "expiring" email: the one deadline a secret has is the end of a rotation's overlap. See Credentials for rotation.
"Your own" means connections of apps that belong to your workspace's organisation. In a house, a vendor's connection gets only the Vendor connections email, with counts: its detail is the vendor's, as in Who sees what in a house.
Your connections in a house
A vendor's connections in a publisher's house belong to the vendor, so the vendor's own vendor workspace gets their emails: Credentials, Daily allowance, Consumer queues and Refusals in houses. They go to whoever your workspace chose for each email, use your lag threshold, and link to Houses you're in. Each email is about one of your connections in one house: it never mentions another vendor's connections, the house's own connections, or the house's settings. The house doesn't get these emails, and never sees the rules behind your refusals.
Who gets them
Each workspace chooses, per email, who gets it:
| Choice | Who |
|---|---|
| Owners (the default) | The workspace's owners |
| Admins and owners | Admins and owners |
| Developers and up (the default for replay and redrive: they start them) | Developers, admins and owners |
| Every member | Everyone in the workspace, viewers too |
| No one | Nobody: the email is off for the workspace |
In the portal, open Notifications in your workspace. Admins and owners change who gets each email and the consumer lag threshold (5 minutes to 24 hours); in a house, also when a vendor's connection counts as silent (1 to 168 hours) and the share of refused messages that is reported (1% to 100%). A person whose sign-in has been disabled gets no emails. Every member can turn any email off, or back on, for themselves.
Stopping an email
Every email ends with an unsubscribe link for that kind of email in that workspace. It opens a page with one button; you don't need to sign in. Mail apps that offer one-click unsubscribe use the same link. To turn it back on, open Notifications in the portal.
What's in an email
Ids, app names, counts and times, and a link to the portal: for example the connection id, how many requests it has made today, or how many messages its dead-letter queue holds. A Refusals in houses email also names the rule ids that refused your messages, with how many each refused. Never message contents, payloads, client secrets, tokens or keys.
How often
The same issue is emailed at most once per cooldown: once per rotation for an ending overlap, once a day per connection for the allowance, and once every 6 hours per consumer queue for a growing dead-letter queue or for lag. A test run, a replay and a redrive are each emailed once. A vendor connection going silent or coming back is emailed once each time (a connection still silent a week later is mentioned again), and its refused share at most once every 6 hours; so is a vendor's own refused share in a house.
A person gets at most 10 notification emails a day from one workspace.
An email is sent at most once. If something fails just as it goes out, you may miss that one email; you won't get it twice.
Records
Changes to who gets what, every unsubscribe and resubscribe, a vendor connection going silent or coming back (in the house's log), and every notification sent (which issue, and to which members, never their email addresses) are recorded in the workspace's audit log.