Operations & Updates

Platform Ops centralizes health checks, integration failures, delivery logs, failed jobs, live operations events, recovery snapshots, backups, update runs, mailboxes, and safe maintenance actions.

Health Checks

The Operations Center checks APP_URL, /login, database access, migrations, scheduler heartbeat, queue health, failed jobs, storage link, writable paths, mail configuration, disk space, installer lock state, deploy smoke status, recent webhook failures, and active inbound mailboxes. Warnings usually mean configuration or background jobs need attention.

Post-Install and Go-Live

• Post-Install Verification: run /operations-center/post-install after a fresh install to verify login route, app URL, installer lock, migrations, storage, writable paths, queues, mail, scheduler, admin role, and AI/provider settings.
• Go-Live Readiness: open /operations-center/go-live before handing the app to users. It brings install readiness, mail, queue, scheduler, permissions, deploy smoke, backup freshness, release acceptance, and AI provider readiness into one checklist.
• Health Export: export a support bundle with health checks, app version, PHP/extensions, DB summary, queue/mail configuration summaries, recent backup runs, deploy smoke status, and sanitized operational context.

Heartbeats

Heartbeats show the last seen time for scheduled jobs and integrations: tickets:check-sla, tickets:run-automations, reports:send-scheduled, inbound mail, and webhook dispatch.

Recovery Actions

• Optimize clear: runs php artisan optimize:clear.
• Queue restart: runs php artisan queue:restart.
• Clear failed jobs: runs php artisan queue:flush.
• Unlock installer: removes storage/app/installed. Use only during controlled recovery.

Release Checklists

Release checklist runs record backup freshness, deploy smoke, /login, storage, queue health, failed jobs, mail, migrations, permissions, AI provider readiness, rollback notes, release name, deploy reference, and formal acceptance metadata. Acceptance records are audited so teams can prove what was checked before a live release.

Demo Mail and Delivery Proof

Demo Mail Center lives under Operations. It gives buyers a realistic email evidence timeline without relying on bulk Gmail or Google Workspace sending. The default mode is log-only simulation, while a capped proof email can be sent through configured SMTP when allowed.

Configuration Snapshots

Recovery snapshots are JSON files saved under storage/app/backups. They include settings, ticket setup, business hours, automations, playbooks, organizations, contracts, status components, API client summaries, and webhook summaries. Snapshots can be imported to restore configuration tables.

System Updates

The update module stores products, releases, licenses, installation records, update runs, and download logs. Admins can save a license, check for updates, upload a package, install a remote update, and roll back supported update runs.

Built-in Runbooks

• Inbound Mail Stall: check mailbox last-received times, failed jobs, and delivery logs.
• Webhook Failure Spike: inspect failures, confirm endpoint health, replay a sample delivery, and rotate secrets if signatures fail.
• Portal Update Backlog: review customer-visible approvals, overdue approval queues, and ownership before escalating.
• Recovery Drill: create a snapshot, review readiness, and validate the latest backup catalog before recovery actions.
• cPanel Release Drill: extract the private and public ZIPs, run the installer, verify /supporthub/login, run post-install checks, accept the release checklist, and save rollback notes.