Deleted queries keep triggering failure event handlers

💬 App Building
1

Hi Retool Team,

I had a query in my apps that was timing out and I made some performance adjustments by creating separate queries. I ended up deleting this original query. This query had a failure event handler which would add a record and send me an email (via retool email) with the details.

However, now that the query has been deleted and new versions of the app released I keep getting the emails any time users use the app. Meaning the query is still running (which triggers a workflow) even though it doesn't exist anymore.

Not sure how to address this and any guidance from the team would be helpful!

3

Hi @MiguelOrtiz,

I haven't seen this before :thinking: but here are my initial thoughts/questions

  1. Is there anything in the Workflow run history that shows it was being triggered?
  2. If you export the app and search for the query name do you see any clues in the app state? Happy to take a look as well
  3. Is the app using release management - curious if users are accessing an older version of the app?
  4. Is this a multipage app or an app with a module? Curious if a similar query is being triggered on another page/module/etc
  5. Do you see anything in the audit logs for the query? Or, could you DM me the name of the query?
4

Hi Tess, apologies for the late reply.

  1. Yes. So the deleted query had a failed event trigger which sent the query info as data. The only id I can see for the query is fetchStaticInfo2 (as in there is no integer id)
  2. Nope, I exported the app and search for the query name and couldn't find it.
  3. Yes, it is using release management and users are accessing the newest version.
  4. Nope.
  5. Nope, nothing here either.

Thanks for looking into this Tess!

5

The circumstances in my situation, which I just posted moments ago, are quite different, involving a module and a parent app.

But the symptom seems similar: deleted queries still being referenced in a strange manner: from a parent app that should be pointing to the Live version of a module where those same queries still exist.

Just thought I'd mention it as I was looking for something in the forums that might've been the same as my issue. Please ignore if this sounds unrelated :slight_smile:

6

Hi @MiguelOrtiz,

Have you narrowed this down at all? @dguzzo's report is helpful to see along side this one, but it seems slightly different.

I know were looking into some strange save behavior, but again, this sounds different :thinking:

I haven't been able to reproduce this or find an exactly similar report, but I was wondering if you could send me an app export?

7

Hi @Tess,

I've sent you the app export. My only concern is whether this queries are impacting performance or not.

1 Like
8

Marking this as solved since we were able to track down the query. It ended up being related to modules

1 Like