Skip to main content

Notifications

Quapp tells you when something you started has finished, and when something changed that affects your account. Notifications appear under the notification bell in the platform header.

The bell shows an unread count. The count updates in real time as new notifications arrive — you do not need to reload the page.

What you are notified about

Job notifications

You receive a notification when a job reaches a final state, whether it succeeded or failed. This covers jobs on simulators, on quantum hardware, and on HPC infrastructure.

Two rules are worth knowing, because they explain what you will and will not see:

  • One notification per outcome, not per attempt. A job that Quapp retries automatically does not produce a notification for each retry. If a retry eventually succeeds, you are notified of the success.
  • Every ending is reported. A job that ends through an internal error path still produces a notification, so a job never finishes silently.

For what the job states mean, see Managing and Tracking Job Results.

Deployment notifications

A function deployment notifies you when it finishes. As with jobs, one deployment produces one notification.

Billing and subscription notifications

Billing events notify the billing owner, which is not always the person using the subscription:

  • A notification is sent when a subscription is purchased.
  • Payment notifications are triggered by the payment result itself, and show the payer's name and the formatted amount.
  • Invoices are de-duplicated, so a single invoice does not notify you more than once.

Workspace notifications

Changing a member's role notifies both the affected member and the administrator who made the change. See Workspace Member Roles.

How long notifications are kept

Read notifications are removed automatically once they pass their retention period, so the list stays relevant.

Unread notifications are never removed automatically. Anything you have not read yet stays until you read it.

Notes

  • The unread count is streamed from the server. If the connection drops it reconnects on its own, so a badge that briefly stops moving does not mean notifications were lost.
  • The Identity Management screens do not carry their own notification bell — notifications are shown in the main platform header.