A comprehensive guide to filtering automated tasks, executing on-demand test runs, inspecting execution terminal outputs, analyzing exit codes, and auditing historical cron logs in MASACP.
Observability and Diagnostic Reliability in Task Scheduling
Configuring a background task is only the first phase of reliable system automation. When scheduled jobs fail silently in traditional crontabs, administrators frequently discover data discrepancies, stalled queues, or expired SSL certificates days or weeks after the fact.
MASACP solves this diagnostic opacity by pairing every scheduled job with real-time process supervisors and structured audit logging. System administrators and website owners can trigger jobs on-demand to verify behavior before committing to unattended execution, inspect exact standard output (stdout) and standard error (stderr) streams, and analyze historical execution telemetry.
Navigating the Scheduled Tasks Registry
The primary registry table organizes all active, pending, and completed tasks into an interactive control center.

1. Filter Tabs and Universal Search
To isolate specific types of tasks in high-density hosting environments, use the category filter pills located directly above the table:
- All Tasks: Displays all registered automation jobs across the server.
- Shell Scripts: Filters for native terminal commands and bash utilities.
- PHP Scripts: Isolates CLI PHP jobs executed via specific PHP versions.
- Access URL: Highlights HTTP/HTTPS webhooks and external URL health probes.
- WordPress Cron: Isolates offloaded WP-Cron queue tasks.
- Server Maintenance: Focuses on system-level daemons (e.g., SSL auto-renewal, log truncation, database optimization).
Use the Search by name, command, or URL… field to locate tasks instantly by entering keywords, domain names, or target binary paths.
2. Registry Table Attributes Explained
| Column Header | Displayed Data | Operational Meaning |
|---|---|---|
| Task Name & Command | Auto SSL Renewal certbot / acme auto check |
The descriptive title alongside the exact executable string or daemon routine. |
| Type | SSL RENEW | Categorical badge reflecting execution architecture and privilege boundaries. |
| Schedule | 0 2 1 * * Monthly on day 1 at 2:00 AM |
Standard 5-part cron syntax paired with an auto-translated, humanized schedule summary. |
| Scope / Site | System (Global) or Domain Name | Indicates whether the task runs system-wide or is confined to a specific website document root. |
| Last Run & Duration | Timestamp & Execution Time | Displays when the task was last executed and its processing duration in milliseconds. |
| Status | Pending Active | Real-time execution status (Running, Success, Failed, Pending) and administrative state (Active / Inactive). |
One-Click Manual Execution (Run Now)
Waiting for a scheduled interval (e.g., waiting until 2:00 AM) to verify script syntax or test API connectivity is impractical. The Actions column features a dedicated Play (Run Now) button for immediate verification.
What Happens During a Manual Trigger:
- The engine bypasses the scheduled timer and dispatches an asynchronous one-shot execution process.
- The command is executed strictly within its designated POSIX tenant context or system sandbox.
- A dedicated terminal modal opens in the interface, showing real-time streaming status (Task executing…).
- Upon process termination, the modal displays the exact Exit Code, total Duration (ms), and complete terminal output.
- Administrators can copy the generated output with one click using the integrated Copy button.
Forensic Execution History Logs & Exit Codes
Clicking the Document/File (Execution Logs) icon in the Actions column opens the historical audit drawer. MASACP retains the last 50 execution events for each task to facilitate post-mortem analysis and performance tracking.
Audit Log Telemetry Data
- Trigger Origin: Distinguishes whether the execution was dispatched via Scheduled automation or triggered manually (Manual Run).
- Start Timestamp: The exact server time when the process was spawned.
- Duration: Execution time recorded in milliseconds to identify performance bottlenecks.
- Exit Code: The standard POSIX process exit status returned by the operating system kernel.
- Terminal Output: Complete standard output and error traces, preserving exact line breaks and stack traces.
Interpreting POSIX Process Exit Codes
| Exit Code | Status | Diagnostic Assessment |
|---|---|---|
| 0 | SUCCESS | Command terminated normally without errors. All script assertions were satisfied. |
| 1 | FAILED | General runtime error (e.g., PHP Fatal Error, unhandled script exception, or database connection timeout). |
| 127 | NOT FOUND | Command not found. The specified binary path (e.g., wp, composer) does not exist in the environment PATH. |
| 137 | KILLED (SIGKILL) | Process was forcibly terminated by MASACP supervisor because it exceeded the configured Execution Timeout or breached memory limits. |
To manage disk utilization and purge obsolete records, administrators can click Clear Logs inside the audit modal at any time.
Task Lifecycle Management & Troubleshooting
Pausing Tasks Without Deletion
If a website is undergoing maintenance or an external API is temporarily down, administrators can pause a task by opening the edit modal and unchecking Enable Task Execution. Paused tasks remain in the registry with an Inactive status and can be re-enabled with one click when maintenance finishes.
Resolving Path Traversal and Permission Denials
MASACP enforces strict tenant confinement. If a tenant attempts to run a script pointing outside their designated user folder (e.g., trying to execute /var/www/otheruser/script.php or /etc/passwd), the security engine terminates the request with an access denial error. Always verify that PHP scripts reside within the website document root.
Safe Task Deletion
Clicking the Trash (Delete) icon triggers a confirmation prompt. Confirming deletion safely unregisters the task from the scheduling loop and purges all related database logs, preventing orphaned processes.