Manage scheduled jobs and maintenance

Check schedule and readiness together

A completed installation enables Obelisk jobs and requests activation of its SQL events. Review the installation result and System and utilities for the settings used by your features. Automatic audio analysis and weekly or monthly reports require AI configuration; scheduled email reports also require SMTP. Recording cleanup and retention need their own deletion switches. Enabling the schedule alone does not authorize audio deletion. Keep retention decisions aligned with the policy agreed for your contact center and its backups.

Pause and reactivate Obelisk processing

1. Suspend for planned maintenance

   From the original extracted installation kit, use this command when the maintenance procedure requires suspending Obelisk jobs and events. Keep any custom path and PHP options used for that installation. This command manages Obelisk processing; it is not a FreePBX shutdown.

   Command

   cd /root/obelisk-install &&
   sudo bash install.sh --disable-jobs

2. Reactivate after verification

   After completing maintenance and verifying the installation, reactivate the jobs deliberately. Check the command result and the next expected executions. Do not run a second process manually just because a scheduled process is still working or a feature remains administratively disabled.

   Command

   sudo bash install.sh --activate-jobs

3. Review suspended analyses

   Use Automatic analysis status to read the suspension reason. Correct the cause before using Requeue. You can select up to 20 items on the current page and confirm the count. An update does not automatically reset attempts or restart suspended analyses.

Keep maintenance observable

Record the maintenance window, the controls changed and the observed result. Distinguish a disabled feature from a failed execution and a test run from an actual scheduled run. Retain installation logs and update recovery material until the corresponding operation is verified. For disk-space housekeeping, use the application’s specific, confirmed cleanup workflows; do not delete SQL data, recordings, private profiles or maintenance markers by guessing which files look old.

Locate a delayed background task

1. Historical processing

   In Database and catalogues, inspect the scheduled database events and their state. Compare the source period with a known report interval before attributing a delay to missing calls. The SQL events and the application’s scheduled server tasks are distinct controls; a working live dashboard does not prove historical processing has completed.

2. Audio and email

   In System and utilities, inspect background processing for waiting or suspended recordings, then review the configured AI and SMTP settings. Correct the recorded cause before requeuing an analysis. For scheduled reports, verify the recipients and the expected weekly or monthly period; generating an AI report interactively does not by itself prove that the scheduled email was delivered.

Open this screenshot ↗

Open this screenshot ↗

Complete product screenshots

Illustrative data. Open the screenshot to enlarge it and match the controls to the instructions in this chapter.

Open complete screenshot ↗