Schedule a fetch from Data Manager
Use scheduling a fetch to keep your Data Manager data updated. Instead of manually starting each fetch or relying on external task schedulers, you can configure a cadence directly within the Data Manager UI for cloud-enabled data sources. Atlassian will then trigger the fetch automatically at your selected time.
Scheduling is currently only available for Cloud-enabled data sources using the Data Manager UI.
This task requires Data Manager & Adapters admin permissions to complete. See how permissions and roles work in Data Manager.
Before you begin
To create or manage a schedule, you must:
Have Data Manager Admin and Adapter Admin permissions.
Have completed at least one manual fetch for the data source.
Supported frequencies
You can schedule imports to run at the following intervals:
Once: A single run at a specific date and time.
Daily: Runs every day at the selected time.
Weekly: Runs on specific days of the week.
Monthly: Runs on a specific day of the month.
How to schedule a cloud fetch
From the sidebar, select Assets.
In Data Manager, select Object classes.
Select the Show data sources button beside the Object class.
Select the data source you wish to schedule.
Select the dropdown from the Fetch section.
Select Schedule cloud fetch.
Configure your schedule:
Frequency: Choose Once, Daily, Weekly, or Monthly.
Start Date & Time: Select when the schedule should begin.
Timezone: Ensure you select the correct local timezone to avoid shifts in execution time.
Click Create.
Once created, the schedule details (trigger time and frequency) will appear in the Fetch section of that data source. You can update or delete the schedule at any time from the same menu.
Snapshots are not currently ran when scheduled from cloud.
Best practices & limitations
Stagger your schedules
To ensure optimal performance, we recommend staggering your imports with at least a 30-minute gap between different data source fetches.
Monthly scheduling (Days 29-31)
If you schedule a monthly fetch on the 29th, 30th, or 31st, the import will only run in months that contain that date.
Example: A schedule set for the 31st will not run in February, April, June, September, or November.
Recommendation: To ensure a run every month, choose a day between the 1st and 28th.
One-time schedules
One-time schedules are automatically removed from the UI after they have successfully run or reached a terminal failure state.
Troubleshooting
Issue | Possible Cause | Resolution |
|---|---|---|
Schedule didn't run | Permissions revoked | Ensure the schedule owner still has both Data Manager Admin and Adapter Admin access. If access was lost, the run is skipped. |
Schedule ran at the wrong time | Timezone mismatch | Check the timezone configured on the schedule. The system honors the users timezone selected during setup. |
Cannot see "Schedule cloud fetch" | Data source has not been fetched once OR the data source is not set with Mode of Connection is cloud to cloud. | Ensure you the data source has been fetched once. Edit the data source and ensure that the Mode of Connection is cloud to cloud. |
Monthly run skipped | Date doesn't exist | Verify if the schedule was set for the 29th, 30th, or 31st in a month that doesn't have those days. |
Was this helpful?