Hey @davidl! Would you mind sharing how you have your disable query fields configured? I'm wondering if there might be something particular to your use case in addition to what's been mentioned above.
I can send a picture but just having a {{ true }} is enough to reproduce this issue, queries will run on app load regardless of the value in the disable query field
As for now we just disable automatic calls and trigger all queries manually in code.
Interesting 
that looks like a bug, but I haven't been able to reproduce it on my end.
Would you mind if we stepped into the affected app to take a look at things directly? I'm curious to see the rest of your query settings and any triggers you might set up. I'm also wondering if this reproduces for you in a freshly created app.
This is absolutely nonsensical behavior. Why would the disableQuery condition changing from false to false trigger the query? Please fix this
Probably because it is checking if the condition changed, not whether the condition evaluates to the same result.
1 Like
I'm having the same issue - the query runs even when "disable query" condition is true
Can you help me, please?
Thanks
Hi @Lior_Rok,
I haven't been able to reproduce an issue where it runs when the condition is true 
Any chance you could share an app export or screen recording?
I haven't been able to reproduce an issue. I tested an external query the same as you and it was controlled by the condition being true.
You might have to console.log() the condition to see what it displays once you select a new table.
Also, make sure that that table is not inside a Repeatable or a table collapsable row, you can't access an components directly inside these components.
Sharing a recording - Companies | Retool - 11 February 2025 | Loom
As you can see the "getEvaluatingCompanies" fetch goes out even when there isn't a value.
It's not a collapsible table 
Hi @Lior_Rok
Thanks for the recording! I think I am following so CompaniesTable.selectedRow.data._id is null within the query, but seems to be defined in the disable condition?
It might be a bug with the table since that version of the table is deprecated. Any chance you could try switching to the new table? Is there a feature from the deprecated table that you're waiting for in the new one?
That said, I am still not seeing the same behavior with the deprecated table 
Can we see what getEvaluatingCompanies is doing and how it is being triggered?
If you can share an app export, I'm happy to take a look there.