Domain separation can prevent data sources from accessing request actions


When configuring a Data Source of Type REST (IntegrationHub) you need to configure a Request action. If the Flow Designer Action that you configure is in a different Domain (for example TOP) to the Data Source (which is by default in the Global Domain) then the Data Source will be unable to use that Action as its Request action.

The error message will be something like: com.glide.plan.runners.FlowObjectAPIException: The action named: your_action_name does not exist within application scope: global

Release or Environment



The Flow Designer Action needs to be in the same Domain as the Data Source, usually Global