What Methods Can Be Used to Separate Error Notifications Between Departments in Pipedream?

1

This topic was automatically generated from Slack. You can find the original thread here.

Hi guys,

I was wondering what ways/methods others are using to keep error notifications seperate between Departments. If turned on for a workflow, Pipedream will send an email if an error occurs. This email does to the sole email address on the account settings which is not applicable in at least 80% of my cases as I help clients deploy and manage their Pipedream instances.

Finance/procurement dont like to get the error notifications and I dont even like the client getting to know about the error before me. I turned on slack notifications but the email still gets the notifications sent to slack so this approach doesnt work.

I thought of an error management workflow that gets all errors and sends to a workflow from where it goes to slack but I’m not sure if this will notify me if the error is a runtime error.

I’m sure I’m missing something on how to address this. I want billing related info to go to finance or whoever I specify and workflow/error related messages come to me.

2

Yes runtime errors will also be emitted to the $errors channel.

So you can set up a workflow to trigger on new errors in the $errors channel and then have smarter routing based on the type of error:

3

There’s also a quick pre-built trigger under the Pipedream app within the builder. So you can just create a trigger based on the $errors channel.

4

Thanks How do I see this pre-built trigger?

5

I have to set up the subscription first yeah?

6

The $errors channel is already created, so you just need to create the trigger in the new workflow to subscribe to it.

Here’s a quick screencast that shows how to find this trigger:

7

Many thanks.

8

Sure thing :slightly_smiling_face:

9

Thanks… I’ve set this up…

Any idea what to expect if this particular WF doesnt get triggered or fails while running?

10

The subscribing workflow should execute on errors events, like any normal workflow when receiving events.

I’ve not personally ran into this issue of failures while running, it might throw those events onto the $errors channel.

11

Got it…