Errors when opening flow - Label cache error: Table not found: _custom_table_in_different_app_scope
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-15-2023 01:32 PM
I get an number of warning messages when opening up a flow using flow designer, all relating to a table in a different app scope. That other app scope was deleted from the instance but I am puzzled where the reference is to that table in the app scope where I opened the flow. The issue is not just on a single flow, it is all flows in the app scope I am trying to edit.
Would anyone know how to find this reference in my app scope? I've gone through the various flows that I opened but there is nothing that ties these flows to that table in the other app scope (as far as I can tell).
These errors show as a warning when opening the flow but show as an error when trying to save it - which then fails.
Thanks
Ron
- Labels:
-
flow designer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-15-2023 03:29 PM
It's not every flow, I suspect these are flows that were copied from flows in the other app scope.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-15-2023 04:05 PM
The errors go away when I re-install the old app scope. The worrying thing is that I have references from a new app scope to a table in the old app scope.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-06-2023 08:06 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-10-2023 03:56 PM
Hi Jophy
Thanks for the link to that article, but I've run the script in our Crash and Burn system and continue to get the errors. The script did remove the references to the table, as running it a second time in debug mode it no longer shows references to that old table.
However, in Flow Designer I continue to get the error, even after clearing browser cache. I suspect the script is quite old and may need updating, it has "gs.print" references in it that require changing for the script to work.
Thanks
Ron