Attached is a data flow, called D3SA_Check_Schedule_Status, that was developed by members of our Professional Services team, Ernest Jones & Stony Smith. The purpose of this data flow is to notify you if any of your scheduled runs fail.
We recommend you run it once every 15 minutes or once per hour. We recommend that you configure the Clean up of Scheduled Runs (see screenshot) before running the data flow. To do this, got to Settings > Scheduling, and input the values that best suits your business needs. Per the screenshot below, we recommend keeping 5 - 10 of the most recent runs, and deleting runs older than 5 or 10 days but it really depends upon the cycle time of your data flows.
Comments
5 comments
Christina Costello we have tried to use the graf D3SA_Stop_Running_Jobs - 11 Jul 2019.lna without success.
The graf finds the jobs we want to stop, but the last node (that does the acutal cancellation) never ends, so nothing get cancelled. Is there any other way to stop a scheduled job?
Hi Sebastien. Sorry for the delay - I needed to speak to the team about this.
Unfortunately, at this time there is no way to stop a running schedule. However, there are ways to troubleshoot scheduled jobs that have become stuck which may help you pinpoint the root of the problem - see here: https://support.infogix.com/hc/en-us/articles/360028934073-Data360-Analyze-troubleshooting-stuck-schedules
We have found some inefficiencies in the Stop_Running_Jobs data flow, so we recommend that you don't use it & we have removed it from the attachments.
We have an enhancement request raised to introduce the ability to manually stop a running schedule; LAE-6671.
Hello Christina,
Was there any progress on LAE-6671 to be able to cancel a scheduled job?
Thank you
Sebastien
The Engineering team have some work in the v.3.10 release that is related to LAE-6671. This change will enable the AnalyzeCli to be used to stop a running execution.
That's great to hear, thank you Adrian
Please sign in to leave a comment.