Skip to content

Notifications#

The bell in the console's top bar tells you what happened that is yours to know or act on. Its badge counts what you have not read, and changes as things happen, without reloading. Choose which kinds also come by e-mail.

What you are told#

Kind Who is told By e-mail too, unless you turn it off
Invitation to an organisation, a workspace or an environment — with Accept and Decline The person invited, when they have an account A reminder, once, if it is still unread after a day
An agent run waits for your approval The people who may decide it: the workspace's editors and admins its approvers name Yes
A deployment was shared with you You, when someone shares an Eos deployment with your address; a workspace's admins, when one is shared with the workspace No
Someone added you to an environment, or accepted your invitation to one The person added; whoever invited No
Your run failed Only the person who submitted the run (from the console, astra or the API) No
A machine is down The organisation's owners and admins No
An e-mail you sent could not be delivered (an invitation, a share) Whoever sent it Never: it is shown in the console only

You also hear when someone accepts or declines your invitation, and when an invitation you accepted could not give you everything it named.

Notifications are yours only: nobody else sees them, organisation admins included. They are kept for 90 days, are part of your data export, and are deleted with your account.

Read and answer them#

  • Select the bell: the latest 20, unread ones marked with a dot. Select one to open what it is about; it is marked read.
  • An invitation shows Accept and Decline in place. Accepting opens the workspace you joined; see Invite people.
  • Mark all read clears the badge. See all opens Notifications, with every notification (older ones with Older), Unread only, and × to dismiss one.
$ curl -sS "$ASTRALYX_API/me/notifications?limit=20" -H "Authorization: Bearer $ASTRALYX_TOKEN"
{"items":[{"id":"0192f3c1-…","kind":"run_failed","title":"Your run train-7 failed",
  "body":"Exit code 1","link":"/o/acme/w/vision/runs/dc1/train-7","data":{…},
  "created_at":"…","read_at":null,"read":false}],"unread":1,"next_before":"0192f3c1-…"}
$ curl -sS -X POST "$ASTRALYX_API/me/notifications/0192f3c1-…/read" -H "Authorization: Bearer $ASTRALYX_TOKEN"
$ curl -sS -X POST "$ASTRALYX_API/me/notifications/read-all" -H "Authorization: Bearer $ASTRALYX_TOKEN"
{"read":3}
Call Does
GET /me/notifications Newest first; limit (≤ 100, default 20), before (the previous page's next_before), unread=true
POST /me/notifications/{id}/read Marks one read
POST /me/notifications/read-all Marks all read
DELETE /me/notifications/{id} Dismisses one
GET /me/notifications/stream Server-sent events: changed with {"unread": n} whenever yours change

An invitation's notification carries invitation_state (pending, accepted, declined, expired, withdrawn) and its ID in data.invitation, to answer with POST /me/invitations/{id}/accept or /decline.

ASTRALYX_API is https://api.astralyx.cloud/v1 and ASTRALYX_TOKEN an API token for all your workspaces; a token scoped to one workspace cannot read notifications.

Choose what comes by e-mail#

Every notification shows in the console. For each kind, choose whether it also comes by e-mail.

Open Notifications (from the bell, Settings) and, under Settings, tick By e-mail too for the kinds you want mailed.

$ curl -sS -X PUT "$ASTRALYX_API/me/notification-settings" \
    -H "Authorization: Bearer $ASTRALYX_TOKEN" -H "Content-Type: application/json" \
    -d '{"run_failed": {"email": true}, "approval": {"email": false}}'

Kinds: invitation, approval, deployment_shared, environment, run_failed, machine_down, mail_failed (console only: 400 EMAIL_NOT_OFFERED). Only the kinds named change.

A notification is mailed only while it is unread, within a day of happening. Turning approvals off by e-mail keeps them in the console: you still see each one waiting for you.

Needs attention, on a workspace's home#

A workspace's Overview starts with Needs attention: at most five short rows, blocking ones first (marked with a red dot), then the newest.

  • Several of a kind are one row — 3 of your runs failed — linking to the list, filtered.
  • Runs are yours only: those you submitted, failed in the last day or waiting longer than 15 minutes. Machines, GPUs, drives and credentials that need attention show to the workspace's editors and admins.
  • × takes a row off your home. It comes back when it changes — another run fails, a machine goes down again — and Show dismissed brings them all back. What you dismissed is remembered for you, on every device, for 90 days.