Schedule A SyncProfessional

Schedule Data Source Sync

Data source synchronization fetches newly added content, deletes removed content, and updates modified content from your original repository. Syncs are optimized to only process changes, ensuring previously successful processed files are not re-processed unless they have been updated.

You can trigger a sync manually or set up an automatic schedule.

⚠️ Permissions: All users can view sync schedules. Only Admins and Platform Admins can create, update, or delete sync schedules.

Schedule a New Sync

1. From the Data Sources list view, locate the data source you want to schedule.
2. Click the options menu on the right side of the data source row.
3. Select Schedule Sync.
4. In the opened dialog, choose your desired frequency:
   • One-time: For a single future sync.
   • Daily: To sync once every 24 hours.
   • Weekly: To sync once per day on specified days of the week.
5. Select the Start date and a Time slot. Schedules are available in 1-hour time slots.
6. Click Done.

Edit or Delete an Existing Sync Schedule

1. From the Data Sources list view, locate the data source with the schedule you want to modify.
2. Click the options menu (usually three dots) on the right side of the data source row.
3. Select Edit Schedule.
4. In the opened dialog, you can:
   • Change the Frequency, Start date, or Time slot.
   • Click Delete to remove the schedule.

     💡 Note: If you delete a schedule, the data source will no longer sync automatically. You will need to trigger syncs manually or create a new schedule.

5. Click Save to apply your changes or confirm the deletion.

If a Scheduled Sync Fails

When a scheduled sync fails, Airia raises a Sync Failures alert naming the data source and the reason it failed, so the failure does not go unnoticed while agents keep answering from content that is out of date. The alert goes to the data source owner and to the user who created the schedule — both, when they are different people; if neither is recorded, it goes to the user whose schedule triggered the run, or failing that to every user in the tenant.

The most common cause is a connection whose credentials have expired or been revoked; re-authorize the connection, then run a sync. See Alerts and Notifications for the full list of causes and for reading alerts through the API.

---

💡 Visibility: The Next Sync and Last Sync columns have been added to the Data Sources, Tenant, and Project list views for improved transparency regarding your sync statuses.