System Tools

A set of operational screens that keep your platform healthy: the background-job monitor, the scheduler status, real-time settings and the audit log.

Queue & Failed Jobs

Location: Admin → Queue (/admin/queue)

Background jobs power campaigns, inbound messages, AI runs and emails. This screen lets you monitor and recover them.

📸 Screenshot: The Queue monitor showing failed jobs and batches.

Two tabs:

• Failed Jobs — any job that errored, with its queue, type and the exception message. You can:
  • Retry a single job.
  • Delete a single job.
  • Retry all failed jobs.
  • Flush (clear) all failed jobs.
• Batches — grouped jobs (e.g. a large campaign), showing total/pending/failed counts and progress.

Cron Setup & Scheduler

Location: Admin → Cron Setup (/admin/cron-setup)

The scheduler drives all time-based tasks (scheduled campaigns, billing sync, trial expiry, social posting, digests, cleanup). This screen shows:

• The exact cron line to add to your server, with your paths pre-filled.
• A list of every scheduled task and its frequency.
• A heartbeat indicator — green when the scheduler is actively running, stale/red when it isn't.

📸 Screenshot: The Cron Setup page with the heartbeat status and task list.

If the heartbeat isn't green, add the cron entry from Deployment:

* * * * * cd /path/to/app && php artisan schedule:run >> /dev/null 2>&1

Real-time Settings

Location: Admin → Real-time Settings (/admin/pusher-settings)

Configure Pusher so the inbox and notifications update live, without storing keys in .env.

📸 Screenshot: The Real-time (Pusher) settings with the Test button.

• Enter your App ID, Key, Secret and Cluster.
• Enable real-time.
• Click Test to confirm a test event fires successfully.

Secrets are masked; leaving a masked field unchanged preserves the existing secret. To self-host real-time instead of Pusher, use Laravel Reverb — see Real-time & Push.

Audit Log

Location: Admin → Audit Log (/admin/audit-log)

A complete, filterable record of sensitive actions across the platform — who did what, when, and from where.

📸 Screenshot: The Audit Log with the action and admin filters.

Each entry records:

• The action (e.g. client.created, subscription.manual_created, impersonation.started).
• The admin who performed it and the user/record affected.
• Old and new values for changes.
• The IP address and URL.

Filter by user, by admin, or by action type. The audit log is invaluable for security reviews, support investigations and accountability — especially around impersonation and billing changes.

➡️ That completes the Admin Guide. Next, see what your customers experience in the User Guide.