Alerts, Jobs, and Updates

Alerts, Jobs, and Updates

Overview

Alerts, scheduled jobs, and updates help platform operators detect issues, run recurring work, and keep CMS services current.

Purpose

Use these operation pages to monitor alerts, review scheduled work, manually run supported jobs, inspect update readiness, and install CMS application updates.

Alerts

Alerts appear in the notification area and Alerts page. They help users identify issues that need attention, such as missing usage, missing subscriptions, region health, identity health, missing billing information, cost issues, or license validity.

Each

recordwhereavailable.

Alert information	Meaning
Title	Short issue summary.
Message	Expected operator action or context.
Area	Feature or platform area.
Type or severity	Importance of the issue.
Related record	Tenant, subscription, region, platform, or other item connected to the alert.
Status	Whether the alert includesis aopen, title, message, area, severityclosed, or type,in status,another andworkflow relatedstate.

Alert Visibility

Users see alerts according to their role and organisation access.

Role	Typical visibility
PlatformAdministrator	Platform alerts and all scoped alerts.
DistributorAdministrator	Distributor, partner, tenant, and subscription alerts inside distributor scope.
PartnerAdministrator	Partner, tenant, and subscription alerts inside partner scope.
TenantAdministrator	Tenant and subscription alerts inside tenant scope.
TenantUser	Tenant-level alerts where enabled.

License validity alerts are intended for platform administrators.

Manual Review Required: The alerts workspace should be reviewed as new system-generated alert sources are added. Operators should confirm the alert message explains the required action before relying on it for a process.

Scheduled Jobs

Administration > Jobs shows scheduled jobs and recent run history for platform roles.

Supported scheduled job types include:

Job type	Purpose
Database backup	Runs configured CMS database backup tiers.
Usage collection	Collects usage and prepares billing-related data.
Usage data cleanup	Removes expired usage data when cleanup settings allow it.
Region health	Refreshes region and identity health.
Delinquent payment notifications	Sends overdue invoice reminders when enabled.
Budget alerts	Sends budget warning or breach notifications when enabled.
License validity	Raises or clears license validity alerts.

The

Key Workflows

Review Alerts

1. Open Notifications or the alert indicator.
2. Filter or search for the alert.
3. Open the related record where available.
4. Complete the required operational action.
5. Close the alert if the process allows it.

Run a Scheduled JobsJob

tab

shows
1. Open type,Administration enabled> state,Jobs.
current
2. Select status,Scheduled lastJobs.
run,
3. Review lastthe status,job status and next run,run.
and
4. Choose description.Run PlatformNow administratorswhere canthe run supported jobs manually.

   Implementation Gap: Region-specific job historyaction is listedavailable.

as an area for improvement. Use the main
5. Review Run History tab when a region detail view does not showafter the expected job entries.
   completes.

Updates

Install

an Update

1. Open Administration > UpdatesUpdates.
lets
2. Review platform administrators reviewthe available versions,version readand release notes,notes.
inspect image tags, check
3. Check service health,health and startbackup CMSwarnings.
application updates.

The update workflow uses

4. Start the Patchinstall Manageraction.
service. The portal shows update
5. Monitor progress and service health from CMS.

   Update pages can show:

   • Available versions for the configured channel.
   • Release notes.
   • Service image tags.
   • Backup-required warnings.
   • Install action.
   • Container health.
   • Update settings.

Access

Alerts are visible according to organisation scope. Jobs and Updates are platform operations areas. Manual scheduled job runs and update installs require platform administrator access.

If

Known aLimitations

user

cannot
• Region-specific seejob ahistory job,may require checking the main Run History tab.
• Rollback UI and signed update action, or alert, check their role, organisation scope, and whether the related feature is enabled.

  Operational Notes

  Before running update or backup-related maintenance, confirm the current backup requirements and the selected update version's warnings.

  Planned Behaviour: Signed manifest verification, rollback UI, and combined multi-service release manifestsverification are listed as future update improvements.