I have a few workflows that are hitting limits and sometimes finding the issue can be difficult, especially when a webhook is triggering hundreds of times in a minute.
Right now I am using the Run History but it only shows 10 by default and you need to click on "load more" for another 10. This is an impossible task when I need to drill down hundreds or thousands.
If anyone has any tips on debugging please share! 
Hi @Shawn_Optipath,
My workaround for this has been to have the first step in the workflow to create a unique value (uuid) and then add a row in a DB with the uuid, run id, run timestamp, sometimes the startTrigger payload, and a "success" boolean column.
Then at the end of the workflow, I update the column based on the uuid to set the boolean to true. This makes it easy to see the failed run, or filter on only failed runs. The run id is part of the workflow debug url, so you can even adjust your row-insert to be
https://{yourDomain}.retool.com/workflows/{workflowUuid}?runId={runId}
So then it's a quick click/copy paste to get directly to the debug. Depending on how many of these you've got, you can use a similar approach with an error handler that send you an email with the URL above, so you get an email that says "There was an email in Workflow X, here is a link to debug".
Hi @MikeCB ,
Sounds like a fun workaround. 
My only reservation with that is I would be inserting and querying that much more and part of my issue is I am bumping against the retool db limit of 1000 queries/minute.
I'll play around with it a little.
