Docebo Connect job failed - is there a way to be alerted when a recipe fails?

Hi ​@sjennings78 
My approach is to use the error capturing blocks and, when errors are caught, send and email with information for diagnostics. For example, in the below, a general "something went wrong" email gets sent if an ‘unhandled’ error happens somewhere in the recipe:
 

And this is the email block settings:
 

It is also possible to trap errors and send emails without stopping the recipe. In the below, an email gets sent if the Jurisdiction field is found to be empty, but it’s not a critical error so the recipe goes ahead and updates the user anyway. 

Hope this helps.

Alan

Thanks, ​@Alan.  We have similar logic in our recipe now to handle errors that happen on the Docebo side.  With this particular issue, it was an error in the processing of a report that is pulling from Workday - the report field was blank and we were trying to check if it contained a specific text string - since the value was Null, it gave an error.  I’ll work on getting logic in place to handle Null values for that field.

Because of the erroneous data (or lack thereof, in this case) for that one field on one row of the report, it caused the job to fail and it did not process any other rows after that, as opposed to having an error and moving on to complete the job. 

What I would really love to see is some sort of generic notification triggered to let us know when any Docebo Connect job fails - a notice of a failed job, not a notice of specific errors captured during the job.  I want to know if the job failed to complete.  I can see that when I go into manage the recipes, but a simple alert notification that automatically applies to all recipes would be nice.

Hello, not sure if this will meet your specific use case but you may want to consider Recipe Ops which can be setup to monitor all or specific recipes including Job Failed triggers.

​@mstrom - thanks for the tip!  Does RecipeOps cost anything to use?  Does that count as another connector on Docebo?

​@sjennings78 you will need to setup a new connection for RecipeOps so I’m guessing it will count as another connector for Docebo Connect. You could double-check with your CSM to be sure. Once you have the RecipeOps connection setup, there are a number of different triggers this connection can respond to, outlined in the Workato docs. So you may find the ROI is worthwhile depending on what your future needs are. Hope this helps.

​@mstrom - I set up the connector and built a recipe to test out.  I was able to cause a recipe to fail and the RecipeOps recipe did its job perfectly - I received an email telling me that the job had failed.  This is great, but I’m pretty sure since it’s using a Connector that it would require us to pay for another Connector.  I’m deactivating the connector and recipe for now, but I will definitely keep those saved in case we decide it’s worth the ROI.  Thank you!!