Skip to content
Orvanta Docs

Critical alerts

Get a notification every time a job is re-run after a crash.

If the node it runs on halts suddenly (such as a power loss), then the job is restarted automatically. Orvanta itself doesn’t crash, and other softer interruptions like a pod termination involve a grace period (300s) to let the job finish.

Critical alerts are generated under the following conditions:

  • A job is re-run after a crash.
  • A license key does not renew.
  • A workspace error handler fails.
  • The number of running workers in a group falls below a specified threshold (configured in the worker group config).
  • The number of jobs waiting in queue is above a threshold for more than a specified amount of time.
  • An API token is about to expire (within 7 days) or has expired (requires “Alert on token expiry” to be enabled in instance settings).

Token expiration notifications

Section titled “Token expiration notifications”

Orvanta monitors API tokens and sends notifications when they are about to expire or have expired. Token owners receive an email notification 7 days before expiration, and again when the token is deleted after expiry.

  • Email notifications are always sent when SMTP is configured, regardless of the “Alert on token expiry” setting.
  • Critical alerts are only sent when the “Alert on token expiry” instance setting is enabled.
  • Session and ephemeral tokens are excluded from expiration notifications.

The tokens table in user settings also shows color-coded expiration badges for tokens expiring within 30 days, and a warning banner for tokens expiring within 7 days.

Critical alert channels

Section titled “Critical alert channels”

You just need to configure SMTP and set up a critical alert channel (an email address) in the instance settings, and/or connect your instance to Slack and Microsoft Teams and fill in a channel name.

You can also set an alert to receive a notification when the number of running workers in a group falls below a given number. It’s available in the worker group config.

Critical alerts in the UI

Section titled “Critical alerts in the UI”

Orvanta itself sends critical alert notifications through the UI. You can disable this in the instance settings.

Visibility

Section titled “Visibility”

Instance-wide critical alerts are only visible to users with the superadmin or devops roles. For workspace-specific alerts, users need admin privilege over that workspace.

Section titled “Related”
  • Worker groups — Configure worker-count thresholds for alerts.
  • Audit logs — Record every operation with side effects.