# CData Sync pipeline - introduce sleep/delay

**URL:** <https://community.cdata.com/t/cdata-sync-pipeline-introduce-sleep-delay/1312>\
**Category:** CData Sync\
**Tags:** question, delay, delays, cdata-sync\
**Created:** [July 13, 2026, 7:46pm UTC](https://community.cdata.com/t/cdata-sync-pipeline-introduce-sleep-delay/1312 "2026-07-13T19:46:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rajesh](https://avatars.discourse-cdn.com/v4/letter/r/8e7dd6/32.png) [@Rajesh](https://community.cdata.com/u/Rajesh)\
**Post date:** [July 13, 2026, 7:46pm UTC](https://community.cdata.com/t/cdata-sync-pipeline-introduce-sleep-delay/1312/1 "2026-07-13T19:46:44Z")

</div>

Is there a way to introduce a delay between steps in a CData Sync Pipeline? We have a limitation from a source API and need to ensure we delay our API requests by 15 seconds between calls, hence looking to add this delay.

---

<div class="post-metadata">

**Author:** ![Ethem\_Q](https://sea3.discourse-cdn.com/cdata/user_avatar/community.cdata.com/ethem_q/32/1997_2.png) [@Ethem\_Q](https://community.cdata.com/u/Ethem_Q)\
**Post date:** [July 14, 2026, 5:19pm UTC](https://community.cdata.com/t/cdata-sync-pipeline-introduce-sleep-delay/1312/2 "2026-07-14T17:19:10Z")

</div>

​ @Rajesh

What you are looking to accomplish should be feasible by using a script in a Post-Job in Windows. The following post from the community should be helpful:

> **[Run bash scripts in Sync Post-Job on Windows | Community](https://community.cdata.com/editions-90/run-bash-scripts-in-sync-post-job-on-windows-819)**
>
> It is possible to run .sh files via sysExecute in Sync Post-Jobs on a Windows installation of Sync, but you have to install a third party program such as bash or cygwin on your machine, which will allow the Windows OS to be able to run .sh files. For...

If you have any issues setting this up, feel free to reach out to the CData support team and one of our Sync Support specialists will further assist you.

---

<div class="post-metadata">

**Author:** ![Rajesh](https://avatars.discourse-cdn.com/v4/letter/r/8e7dd6/32.png) [@Rajesh](https://community.cdata.com/u/Rajesh)\
**Post date:** [July 29, 2026, 12:36pm UTC](https://community.cdata.com/t/cdata-sync-pipeline-introduce-sleep-delay/1312/3 "2026-07-29T12:36:14Z")

</div>

For future reference, another option was to setup the components needed to use Python in the scripts and use the sleep command to incur a delay. This is the option we went with, though the above option also worked for us.