4
Using sentry to monitor errors in Flows
Source: directus/directus#23783 · opened by @danybol
Summary I've managed to get some Sentry error logging working using something like the approach here: This works fine for errors that occur at application startup or during a request - I can see the errors coming through into Sentry. However, for some reason it doesn't seem to work with errors that are raised/logged in Flows. I've tried both uncaught errors and using console.error - they show up in stdout but don't show up in Sentry. I'm hoping this is just some setup/configuration issue on my part, but I've tried a lot of different approaches without success. Since it does log some errors it makes me think that flows are somehow executed differently (not sure if they're executed in a subprocess or something?) Basic Example _No response_ Motivation It's very important for us to be able to track errors in flows because we have some reasonably complicated logic which needs to run. Flow outcomes are tracked in the database but we don…
No pledges yet. Be the first to back this.
Comments
Similar requests
Import and export option for flows
82 votes · 0 comments
Insufficient documentation about blocking and non-blocking flows
3 votes · 0 comments
Enhancing Directus Flows: Versioning, Archiving, and Improved Manageability
28 votes · 0 comments
Add Sorting for Manually Triggered Flows
3 votes · 0 comments
Disable flows from running on a specific directus instance
2 votes · 0 comments
No comments yet.