Overview
Timely Jobs enable the automated execution of workflows without manual intervention. By scheduling a job, you can ensure that critical business processes, such as daily data syncing, weekly reporting, or monthly auditing run exactly when needed.
Scheduling Options
When creating a Timely Job, you can choose between a single execution or a recurring cycle.
1. One-Time Job
Ideal for specific, non-repeating tasks like a system migration or a scheduled month-end report.
- Requirements: * Scheduled Date: The specific calendar day for the execution.
- Hour of Run: The exact time the workflow should trigger.
2. Repeating Job
Used for continuous operations. The platform supports four frequencies:
| Frequency | Required Configuration |
|---|
| Hourly | Runs automatically every 60 minutes. |
| Daily | User specifies the exact Hour of the day to trigger the run. |
| Weekly | User selects the Day of the Week (e.g., Monday) and the Hour. |
| Monthly | User selects the Calendar Date (1st–31st) and the Hour. |
Workflow Configuration & Slots Pre-feeding
Once the schedule is defined, the next step involves connecting the job to your logic.
Selecting a Workflow
You must choose an active workflow from your library. The system will automatically detect and display all Slots (variables) defined within that workflow.
Pre-feeding Slot Values
Since Timely Jobs run autonomously, you must “pre-feed” all required data into the slots:
- Static Values: Provide the fixed strings, integers, or lists required for the agents to operate.
- Contextual Data: Ensure any file references or IDs are valid at the time of execution.
Execution Integrity
Because Timely Jobs are automated and do not have a “Human-in-the-Loop” by default during the trigger phase, data integrity is critical.
Critical Requirement: Any slot mismatch, missing mandatory value, or type inconsistency will result in a non-successful execution.
- A slot expected an
Int but received a String.
- A required
File slot was left empty.
- The Workflow logic was changed, but the Timely Job configuration was not updated to match the new slots.
Monitoring & Status
| Status | Description |
|---|
| Scheduled | The job is waiting for its designated time. |
| Running | The workflow is currently executing agents. |
| Completed | The run was successful and all nodes finished. |
| Failed | Execution stopped due to slot mismatch or agent error. |
Before scheduling a Repeating Job, run the workflow manually once with the exact values you intend to pre-feed to ensure all nodes resolve correctly.
