Manual Guide: Job Logs¶
The Job Logs module is the core monitoring center for all asynchronous tasks and background workers within the system. It aggregates jobs originating from various triggers—including Async Webhooks, Schedulers, SQL Monitors, File Monitors, and Stream Monitors.
1. Interface & Architecture Overview¶
The Job Logs page is structured to handle master-detail monitoring for large-scale background processing:
- Job Log Table (Parent Row): Displays the high-level execution summary of the background task (Source type, trigger source, execution duration, and overall status).
- Child Row (Expandable): Each parent job row can be expanded to reveal granular sub-tasks or execution steps linked to that specific job.
- Dual-Tab Interface: The module splits monitoring views into two main perspectives:
- Tab 1: Job Logs (Master): Overview of main background tasks across all triggers.
- Tab 2: Row Logs (Detail): Granular tracking of individual item lines or sub-execution blocks processed within those jobs.
2. Status Reference¶
Job Status (Parent Level)¶
The main job tracks the aggregate lifecycle across different triggers (Webhook Async, Schedulers, SQL Monitor, File Monitor, Scheduler, Stream Monitor):
| Status | Description |
|---|---|
| Pending | Job has been registered in the system queue but is waiting for worker allocation. |
| Queued | Job is successfully placed in the execution queue, ready to be picked up. |
| Running | Worker is actively executing the job tasks. |
| Success | The job finished executing successfully without any issues. |
| Failed | The job execution encountered a critical failure and stopped. |
| Skipped | Job execution was bypassed due to predefined conditional logic or rules. |
| Completed | The job has finished its entire lifecycle successfully and wrapped up. |
| Partial Success | The job finished, but some non-critical background components encountered issues. |
| Error | An unexpected system exception or error occurred during execution. |
Row Status (Child / Detail Level)¶
Individual rows or sub-tasks inside the child execution breakdown follow this status tracking:
| Status | Description |
|---|---|
| Pending | Sub-task or item is waiting in line to be processed by the worker. |
| Running | The specific row/item is actively being processed. |
| Success | This particular item processed successfully. |
| Failed | Processing for this specific item failed. |
| Skipped | This individual item was skipped based on filter or data rules. |
| Completed | The row item finished its processing pipeline completely. |
| Partial Success | The item processed with minor warnings or non-blocking issues. |
| Error | An exception occurred while processing this specific row/item. |
3. Key Feature: Reprocessing Jobs & Rows¶
If a job or a specific row encounters an issue (such as Failed, Error, or Timeout), you can re-execute it without having to recreate the source payload manually.
How Reprocessing Works:¶
- Locate the stuck or failed Job or individual Row item.
- Trigger the action to re-process (change the status back to Pending via the UI action).
- Once updated to Pending, the task is automatically pushed into the Redis queue.
- The background workers will automatically pick up the queue payload and re-run the process seamlessly.
4. Key Navigation & Child Row Features¶
- Expandable Child Rows: Click the toggle/arrow icon on the left side of any Job Log row to unfold its child records, allowing you to inspect sub-tasks instantly without navigating away.
- Tab Switching: Use the top tab navigation to switch between high-level Job Logs and granular Row Logs depending on the depth of troubleshooting required.
5. Standard Table Operations¶
For complete guidelines on how to use standard table utility features (such as ColVis, copying data, Export/Import, Refresh, Bulk Delete, etc.), please refer to the Standard Tables Guide.