There are important considerations when you schedule CloudWorks integrations.
You should assess integration performance, run times, and look for any bottlenecks. Review your integration schedules often, and especially when you add a new integration. Talk to your colleagues who also schedule CloudWorks integrations. Follow the tips below to run your integrations as efficiently as possible.
| Do this | Avoid this |
| Stagger integration start times at different hours of the day. When integrations run simultaneously, they can slow down | Don't schedule integrations to begin at the same time of day. |
| Run integrations fewer than five at a time across all your models. | Don't set more than five integrations to run at the same time. |
| Schedule one integration at the time from the same model. | Don't set multiple integrations from the same model to run at the same time. |
| Schedule an integration to repeat at an interval greater than 60 minutes. | Don't schedule an integration to repeat within 60 minutes. |
| Schedule an integration to start a few minutes after the hour mark. Examples: 6:42 a.m. or 8:11 p.m. Why? This approach helps distribute tasks more evenly throughout the hour, reducing the likelihood of too many integrations running at once. | Don't schedule integrations to run at the top or middle of the hour. Examples: 8:30 a.m. or 4:00 p.m. Also avoid the minutes right after or before the top of the hour. Examples. Yes 4:04 p.m., no to 5:58 a.m. or 5:59 a.m. |
| Maintain clear documentation of integration schedules, which include start times and task dependencies. | Don't set and forget your integrations. Check runtimes and talk to colleagues who also schedule CloudWorks integrations. |
| Recognize that CloudWorks is anchored to Coordinated Universal Time (UTC). Our integrations shift by one hour per your local time, in zones where daylight savings applies. | Don't forget about daylight savings time. Plan for these time shifts twice annually. |
