After further examination it looks like what is actually happening is if a record is found then the data is returned by a single query but if not found no output at all results where i would expect the query to be returned but with no data i.e an empty data set
I also noticed this sometime ago, but then my steps changed so did not dig into it.
It could be a change in the way Wappler handles null output. @patrick would know.
A normal query returns an array and an empty array when there are no results. Using single query the record object is returned and when there is no result it returns NULL.
The output from the global and the action are being merged together, perhaps the merge is ignoring the null values. Will have a look at it.
I have the same issue but bigger. I tried single, multiple and even paged query. None of them are returning the output.
Any suggestion on how I can fix this situation.
There is something wrong with your server configuration from the looks of it.
Re-deploy the app and try again.
Or, if you can run it locally on your machine, that would be the best test of your code and would confirm the issue being on your deployment and not Wappler.
Also, given that this is completely unrelated to the post here, it would be best to open a new post in the future.