Unable to run Flows that make Callouts about sfdx-mass-action-scheduler HOT 6 CLOSED

Unfortunately, the error System.CalloutException: Callout loop not allowed is behaving as designed by Salesforce.

Per their documentation, the scenario occurs when a Salesforce org makes a callout to a Salesforce org, and then that Salesforce org makes a callout.

Salesforce A ----Callout----> Salesforce B ----Callout----> Webservice

With Mass Action Scheduler, the app invokes your process/flow via a callout to the REST API, so that's the Salesforce org makes a callout to a Salesforce org first part of the scenario. Your org makes a callout back to itself. Then, if your process/flow/apex makes another synchronous callout or uses external services, that is the and then that Salesforce org makes a callout second part of the scenario.

As a workaround, you might try having your invoked process/flow/apex perform its callout or use of external services asynchronously via batch or queueable apex.

There isn't anything I can change here for now until Salesforce provides a way for invocable processes and headless flows to be initiated from apex natively rather than having to go through the REST API. I have brought up this limitation to Salesforce product management and awaiting prioritization.

Note, in Spring 18 release, autolaunched flows can be started from apex natively, but the REST API that Mass Action Scheduler uses to know which flows/processes you want to invoke does not distinguish between invocable processes and autolaunched flows, and so the app cannot reliably know which code path to go down once you've made a a selection.

If/when apex supports starting invocable processes, then I'll revisit this feature request. Please consider submitting this idea on IdeaExchange too.

Thanks!

from sfdx-mass-action-scheduler.

from sfdx-mass-action-scheduler.

Thanks for the kind feedback @bruceleestewart.

Since this is blocked by Salesforce's architecture, and I'm not sure if that limitation will change, I'm going to close this issue for now. I've added to the FAQ.

Thanks

from sfdx-mass-action-scheduler.

This may be a limitation in how Mass Action Scheduler works. The app uses the Salesforce REST API to invoke the chosen action (flow). So what I understand in that help article is that the callout from the flow itself is being blocked because apex code already made a callout.

For grins to see if this workaround helps, could you try adding a flow Wait element before the flow calls the external service? That might cause a new apex transaction to occur and so reset the http callout limit. I’m not saying that is or isn’t a good thing to do, but something to try.

from sfdx-mass-action-scheduler.

@bruceleestewart I'm going to escalate to the Apex and Flow teams to see if this is "by design" or "fixable".

from sfdx-mass-action-scheduler.

Hi @bruceleestewart, could you please share a simple code sample for invoking the External Service I could use to build a reproduction of your issue? Thanks

from sfdx-mass-action-scheduler.