We have created YepCode to give you the best user experience, that’s why it has both fully development and execution environments. This makes it possible that you don't have to leave the platform to create a complete and successful automation or integration.
Once you have written the source code of your process in the editor and run it, the execution of this process may fail due to many circumstances: maybe some of your services is down, some credential has expired, your execution exceeds YepCode limits,...
Whatever the case, you will probably want to be aware when this happens so that you can fix it. A practical solution may be to send the error notification by mail or to a Slack channel, but in any other cases you'll want to retry that failed execution.
We have recorded a video in which we show you how the YepCode error handler works. But let's explain it a bit more.
First, we have created a process that throws an error on purpose. When we run it, an alert crops up showing that the process has failed to show the error trace, and the execution status ends with an error.
A process which you want to configure to handle the errors of the executions has a predefined parameters schema.
In our docs, you can download some sample process templates we have, one that uses Nodemailer to send an email with the error, and the other, which sends the error to a Slack channel using SlackBolt integrations.
In the next step, we are going to download and import the send email template.
Once imported, we need to create the SMTP credential to deliver the email. You could use one Google Account SMTP configuration. In our case, we are using the Sendgrid service.
Then we need to do some changes in the source code to fit our needs, changing email addresses and YepCode team URLs.
After that, we could configure this process as our error handler on the settings page.
Finally, if we run again the failing process, we'd receive an email informing us about the error.
Take a look at this video to watch all the steps to configure the error handler in YepCode and,