Forum Discussion
Thanks to the feedback from Mark and Chayce, my pipeline is successfully running a refresh on the connected table. However, the pipeline job completes upon kick-off of the refresh instead of completion of the refresh. My plan was to add a second step in the pipeline to execute a table import but this won't work if the the refresh/sync is still running. Am I missing something or do I need to keep these two steps in separate pipelines and schedule the second job (import job) with a few minutes lag to allow the refresh to complete?
Thanks again for the help!
------------------------------
Christine Carpentier
------------------------------
- ChayceDuncan2 years agoQrew Captain
You'll have to impose your own delay outside of the refresh. The refresh action isn't like an API call with a callback upon completion so there is no way to bind the two pipelines together. You can take a look on average at how long the refresh takes and either add a 'wait' into the pipeline or just schedule the second one to be slightly after the first.
------------------------------
Chayce Duncan
------------------------------