We encounter dozens of failed Jobs each day, from a couple of dozen different Recipes. Only rarely do these Job failures relate to data or processing issues that need to be addressed. Instead, 95% of them are connection related, and simply require a manual rerun of the failed Job.
We have configured some of our Recipes to avoid requiring failed Job management, by using a Timed Trigger and a data state as an indicator for data processing. For example: the query of a data table based on certain attributes. Employing this allows us to ignore failed Jobs as the next Job run should pick up where we left off.
However, we do need to have certain Recipes that require Triggers that employ real-time record creates/updates. For these Recipes failed Jobs need to be addressed.
It would be great if there was a construct that allowed us to gather the failed Job IDs for particular Recipes, and then dynamically resubmit them - I would assume through a different Recipe.
We could then greatly reduce the amount of management required for our Recipes.
Best Answer
A
Amanda Wong
said
almost 7 years ago
Hi there, have you checked out RecipeOps by Workato? You can create a recipe to trigger on failed jobs and rerun failed jobs. Let us know if that works for you
Answer
Amanda Wong
said
almost 7 years ago
Hi there, have you checked out RecipeOps by Workato? You can create a recipe to trigger on failed jobs and rerun failed jobs. Let us know if that works for you
Scott Hunt
Dynamically rerunning Failed Jobs
We encounter dozens of failed Jobs each day, from a couple of dozen different Recipes. Only rarely do these Job failures relate to data or processing issues that need to be addressed. Instead, 95% of them are connection related, and simply require a manual rerun of the failed Job.
We have configured some of our Recipes to avoid requiring failed Job management, by using a Timed Trigger and a data state as an indicator for data processing. For example: the query of a data table based on certain attributes. Employing this allows us to ignore failed Jobs as the next Job run should pick up where we left off.
However, we do need to have certain Recipes that require Triggers that employ real-time record creates/updates. For these Recipes failed Jobs need to be addressed.
It would be great if there was a construct that allowed us to gather the failed Job IDs for particular Recipes, and then dynamically resubmit them - I would assume through a different Recipe.
We could then greatly reduce the amount of management required for our Recipes.
Hi there, have you checked out RecipeOps by Workato? You can create a recipe to trigger on failed jobs and rerun failed jobs. Let us know if that works for you
Amanda Wong
Hi there, have you checked out RecipeOps by Workato? You can create a recipe to trigger on failed jobs and rerun failed jobs. Let us know if that works for you