Trace Query Triggers

[tspecht]

Hello,

I am running into an issue where a JS query is running on page load even though the setting for this is turned off (I tried toggling it as well).

I was wondering if there is a way to get a list or trace of all queries and how they are connected. That way, I can trace to see why this one JS query is running unexpectedly.

I saw some older forums that mentioned TriggeredbyID, but that does not appear to work anymore. I also attemped to get to a previously mentioned Dev console which showed a map of queries/ components, but that appears to be a legacy item now.

[dcartlidge]

The timeline tab on the debug console would tell you what fires and the state tab will tell you what controls that query, if anything

Debug Tools | Retool Docs

[tspecht]

Ah! Not sure how I missed that on the state tab. Thank you!

Do you know if there is a visual web/map of the queries and components as well?

There was something the retool showed in 2021 that looks like what I am hoping for. Although I think this was before the debug tool was added,

Get a stack trace of how queries were triggered

Hey (2 months ago) Bradly! Are you still seeing this behavior? There's a secret (not polished, not released, not fully-developed or supported) developer panel that might be helpful in cases like these! ctrl + ` (backtick) will bring it up. It has a query dependency tab that gives you a graph of your components and queries. You can even select a specific query to see who it's running and who's running it! In general, the more heavy and complicated the app, the longer it'll take for this pan…

[dcartlidge]

nope, later in that thread they confirm it was deprecated in favour of the debug panel
The tracing is there though, it shows a stack of what ran and what triggered it, just take a look at the success messages in the Console tab and it'll tell you what ran and why, just like the Chrome debugger does