Remote Tables Plugin Uses App sys_id Instead of Scoped App Name When Calling Flow

[giuntaA]

Hi all,

I’m experiencing an issue with the Remote Tables plugin in my scoped app. When the plugin attempts to call a flow, it uses the app’s sys_id as the scope name, rather than the expected scoped app name. This is causing flow execution failures, as the system cannot locate the flow under the sys_id-based scope.

For example, instead of calling the flow as x_example_scope.get_remote_mid_servers, it tries to call it as <APP_SYS_ID>.get_remote_mid_servers.

Here’s a log snippet illustrating the problem (with placeholders for privacy):

[RemoteTable] FlowEvaluatorProvider: Unable to run flow: <APP_SYS_ID>.get_remote_mid_servers for remote table: <REMOTE_TABLE_NAME>: com.glide.plan.runners.FlowObjectAPIException: The flow named: <APP_SYS_ID>.get_remote_mid_servers does not exist within application scope: global: com.glide.plan.runners.FlowObjectRetriever.getFlowObjectRecord(FlowObjectRetriever.java:94)

I have tried deleting and recreating both the Remote Table definition and the flow, but the issue persists.

Has anyone else encountered this? Is there a configuration or workaround to ensure the correct scoped app name is used when the plugin calls the flow?

Any insights would be greatly appreciated!