Global error handler in apps

💬 Feature Requests
1

I hope there's a better way to do this already that I'm missing, but here's my thoughts:

Use case - I need to log errors for later analysis, and be alerted when errors are happening in my apps

Current situation - I create a slack query that sends messages to a monitored channel.
I then have to wire every query to send data to that slack query in the failure event handler. Extra complication is that the slack error handler query needs details about what failed and why and the event handler dialog doesn't have additionalScope or a way to pass parameters, so I have to use runScript to trigger the query.

Ideal situation - nominate a resource as a global error handler for all app queries that automatically receives the query error/context/user/app/ etc and be able to enable this at a global level in addition to individual queries being able to have their own error handlers.

Perfect situation - Also be able to choose the "show notification on success/failure" checkbox option at the app level

1 Like
2

Hey @dcartlidge! I think you're probably doing the right thing...out of curiosity, what kind of errors are you looking to log? Just general query errors?

And I filed requests for both adding additionalScope inputs to the trigger event and for enabling failure/success handling at the app level!

3

That's perfect, thank you!

And, yep any/all errors that occur - I have a particular app with an autosave feature in it that users expect to be bulletproof so trapping everything that might go amiss is vital. Aside from that I need to know when queries fail due to a test case I'd not expected etc.

4

Hi @dcartlidge,

I'm sure this will get added in time, in the meanwhile we're using an implementation like this:

Main JS query to manage failures

var queryData;
const queryOmits = ['dataArray', 'rawData', 'transformer', 'errorTransformer', 'query'];

const cleanedQueryData = _.omit(queryData, queryOmits);
const metadata = {
  currentUser: _.omit(_.cloneDeep(current_user), 'groups'),
  localStorage: _.cloneDeep(localStorage.values),
  retoolContext: _.cloneDeep(retoolContext),
  urlparams: _.cloneDeep(urlparams),
  viewport: _.cloneDeep(viewport),
  navigator: {
    userAgent: window.navigator.userAgent,
    platform: window.navigator.platform
  }
}

And then on each query we want to monitor we add a "Run script" failure handler:

captureFailure.trigger({
  additionalScope: {
    queryData: self
  }
})
2 Likes
5

@dcartlidge is that Autosave feature something for when users are typing into a text area, for example? If so, is that a retool component or something you built to work in Retool?

6

yes that's what I use it for, as changes are made they are saved (after a pause in user activity) without them hitting a save button - it's hand crafted, I don't believe there's such a component or option out-of-the-box

7

:wave: We haven't fully solved for this, but we did add global settings for success/failure notifications here

8

Just bringing this back to life, hoping this may be in the roadmap sometime soon.

1 Like
9

Hi @MiguelOrtiz,

I just looked up the ticket that was attached to this thread, and it seems it was for "configuring the global Query success (or failure) notification suppression" which Tess links to another post, which has been completed.

I am guessing you are getting back to the original issue of this post, not suppressing a query's notification but having a global source of logging errors from queries and components?

Let me know what you imagine to be the ideal scenario for catching query/component errors and being able to output them, and I can write that all up in a new ticket to our eng team. I have a feeling this may already be an existing ticket but would love to get more input to add on or create a more specific ticket if needed.

Also now that @dcartlidge solutions architect at Retool we can have an internal champion for some global error handling :tada: