We have on prem 3.75.14.
Suddenly in one of the multipage apps we can no longer run queries manually - by manual I mean clicking the 'run' button. The query errors with 'query run failed'. This is now happening for all queries! This happens for all queries, including javascript and resource queries.
I created a brand new query - same problem - get the message 'Query run failed' with the lower message that says: 'message: undefined' - so not really much help.
I created a duplicate copy of the app - same problem.
Other multipage apps running fine - so soething has gone wrong with just this particular app!!!
The queries run fine automatically (when called from within the app) but obviously we cant progress and test new development in the app in this way. We have effectively come to a halt on a business critical application. Urgent assistance required!
Hi,
There are no errors showing at all in the history, so trying to randomly pick a point to try and restore to is going to take a while as i have 118 pages of changes.
My concern is how did this happen and why is the app not running the queries ;manually' but. ok in auto.
We really need to get to the bottom and find the cause of this problem and make sure it doesnt happen.
Just jumping in on this thread to point out that we started experiencing a similar problem yesterday where queries can not be manually run, they will run initially on page load but then can not be triggered again by button or automatically. The queries becomes bugged out, and will only run again on a full page reload.
Apologies for this issue. Very odd that only one of your apps are not able to trigger queries to run manually via the run button.
Let me investigate to see if there is an incident on our end this could be related to. @OLR are you having this issue for only one app or multiple apps? Are you hosting your apps on prem?
@peter.b Did you recently update your on prem instance to 3.75.14 or are there any other events that occurred before this issue arose? You may need to check your Docker logs to see if there is a more descriptive error on query fail. We have docs for checking docker logs here.
Will raise this with out internal team and report back any details!
Appreciate the quick reply, hoping to get this resolved asap as its a large holdup.
So far I have only noticed this in our one Multi-page app. We use Retool Cloud.
I have a page load query that runs a JS query that triggers refreshes for table data sources. Its hard to Pinpoint what is going on as 4 of 4 triggers in the JS run on initial web page load, as seen in the network requests. But then as soon as you navigate to another page, and then come back only 2 of 4 queries run, there is no errors, nothing shows up for them in the network requests, we know that the query is correct since it will return the information we need on first page load.
This is fresh page reload where it makes the 4 network requests needed to refresh the data.
@OLR Thank you for sharing those details and the screen shots! Very helpful.
Ok so your issue is also odd, but seems to be different than the unable to manually run queries issue that @peter.b is experiencing. Since you are on cloud we might be able to pull up more details to see what could be going on.
If both of you could DM me an export JSON of your app for me to clone and test out that would be super helpful for me to troubleshoot what could be causing these issues.
I put a empty query on page scope that is supposed to run on page load with no actual SQL that on success calls a JS query that has the 4 queries that I want to run. They are a mix of page scoped and global scoped.
The one issue I see with this being the source of the problem is in my screenshot you will see global_get_user_awarded_not_set_up in both screen shots, that is a global query that runs on both events.
While the one I have been focussing for debugging global_get_current_user_bids only runs on the initial load.
We prefix our queries in multi page with the page name or global pending where they reside.
So we discovered by accident what the cause of our issue was.
We had created a page called 'error' and that cuased the 'Query run failed' issue.
When we renamed the page to something else, the issue went away.
Checked the docs and there is nothing in there about reserved page naming - so need to flag this as a bug in 3.75.14
