Background worker and operations reference

Prerequisites and authority

Use this reference with your installed release. Internal implementation routes and settings are not public integration contracts.

Background worker reference

The generated service inventory identifies each worker declared in the inspected release Compose file and its Python runner. Use it to match a failed operation to the relevant container. Do not substitute historical development timings for current supported schedules.

Work family	Intended responsibility
Subscription maintenance	Activation, expiry and queued entitlement transitions
Payment maintenance	Payment lifecycle/reconciliation
Router maintenance	Managed router reconciliation/session work
Network sampling	Network observations used by reporting/accounting
Notifications	Pending delivery processing
Imports / integration sync	Institutional batches and source synchronization
Reports / analytics	Report and summary production
License verification	Periodic authority verification
Release updates	Release/update coordination
Backups	Scheduled encrypted backup processing

These summaries explain worker responsibilities, not a guarantee that every job runs on an exact interval. Check the operation history, current settings and worker logs for execution, retries and failures on your installation.

Operational evidence should include trigger, start/end, status, processed/succeeded/failed counts, error and target identifiers. A successful run with zero eligible work is different from a stuck runner.

Manual runs require authorization and repeatability checks. Never assume all jobs are idempotent because one payment path is. After manual recovery, verify the next scheduled run. Use Health checks, background services and workers and Worker, provisioning or scheduled task failed for procedures.

Inspected service inventory

Service	Container	Runner/role
`mysql`	`bryannet-mysql`	`mysql`
`api`	`bryannet-api`	`api`
`subscription-worker`	`bryannet-subscription-worker`	`python -m app.workers.subscription_maintenance_runner`
`organization-import-worker`	`bryannet-organization-import-worker`	`python -m app.workers.organization_import_runner`
`integration-sync-worker`	`bryannet-integration-sync-worker`	`python -m app.workers.integration_sync_runner`
`payment-worker`	`bryannet-payment-worker`	`python -m app.workers.payment_maintenance_runner`
`router-worker`	`bryannet-router-worker`	`python -m app.workers.router_maintenance_runner`
`network-sampling-worker`	`bryannet-network-sampling-worker`	`python -m app.workers.network_sampling_runner`
`notification-worker`	`bryannet-notification-worker`	`python -m app.workers.notification_maintenance_runner`
`report-worker`	`bryannet-report-worker`	`python -m app.workers.report_maintenance_runner`
`analytics-snapshot-worker`	`bryannet-analytics-snapshot-worker`	`python -m app.workers.analytics_snapshot_runner`
`release-update-worker`	`bryannet-release-update-worker`	`python -m app.workers.release_update_runner`
`license-verification-worker`	`bryannet-license-verification-worker`	`python -m app.workers.license_verification_runner`
`backup-worker`	`bryannet-backup-worker`	`python -m app.workers.backup_recovery_runner`
`bot`	`bryannet-bot`	`python -m bot.main`
`admin`	`bryannet-admin`	`admin`
`customer`	`bryannet-customer`	`customer`

Exact cadence/locking/retries are not established by Compose declarations.

Background worker and operations reference

Prerequisites and authority

Background worker reference

Inspected service inventory

Related guides