Choose an Auto-Sync Trigger
What Trigger controls
The Trigger step decides when a matching file is processed and how failures or duplicates are handled.
The current choices are:
| Choice | Behavior |
|---|---|
| Immediately | Processes the file when it is uploaded. |
| After a delay | Waits a selected number of minutes or hours. |
| On a schedule | Processes at a recurring hourly, daily, or weekly time. |
Immediately
Choose Immediately when Knowledge should update as soon as matching files arrive. No additional timing fields appear.
This is suitable for finalized content that users need soon after upload. Use a delayed or scheduled trigger when uploads are frequently replaced or when processing should run at a controlled time.
After a delay
Choose After a delay, then enter:
- a positive delay value; and
- minutes after upload or hours after upload.
The page shows a human-readable timing summary. Use this option when a file is likely to be replaced, signed, or finalized shortly after its first upload.
On a schedule
Choose On a schedule, then select:
- Every hour;
- Every day; or
- Every week.
For a weekly schedule, choose the day. For daily and weekly schedules, choose the hour and one of the available minute values (:00, :15, :30, or :45). Then select Zone.
Always read the timing summary before saving, especially when the Workspace operates in a different timezone from the administrator.
Configure Reliability
The same Reliability controls apply to all trigger types:
| Setting | What it does |
|---|---|
| Retry attempts if it fails | Sets how many automatic retry attempts are allowed, from 0 to 10. |
| Wait between retries (minutes) | Sets the delay between retry attempts in minutes. |
| Skip files that have already been processed (recommended) | Avoids processing identical file content again. |
Keep duplicate prevention enabled when multiple rules can match the same source or users commonly upload the same file more than once.
Choose the right trigger
- Use Immediately for stable content that needs to become searchable quickly.
- Use After a delay when the file may change soon after upload.
- Use On a schedule for predictable batch processing or off-peak operation.
- Use Run Now separately when existing matching files must be processed; changing a trigger does not itself backfill historical files.
Troubleshooting
| Problem | What to check |
|---|---|
| A delayed job has not started | Confirm the delay value and unit, then review Job History. |
| A scheduled job runs at the wrong local time | Edit the rule and correct Zone, hour, and minute. |
| A failed job is not retried | Confirm that retry attempts is greater than 0. |
| The same content is skipped | Duplicate prevention found that the file content was already processed. |
| Existing files remain unprocessed | Click Run Now on the rule card. |
