SubFlow - Constant 500 Errors

I am trying to build a SubFlow to retrieve an AccessToken from my webstore so I don’t have to repeat the code repeatedly, but no matter what I do, I get a 500 error in response from the SubFlow. I am on self-hosted, unsandboxed.

The SubFlow itself is working and sending the response but the SubFlow call in my other assembly lines is responding with 500… What should I check?

Hi there.

Could you please show us the the errors you are getting ? if it is responding with 500 it could be the webstore api failing to get you the said access token, if you can share the flow and the subflow as well that would be perfect.


Here are the best images I can give with out exposing security keys. But the SubFlow test works fine it fails when it is called.

Can you send us the link for the flow ?

Hi @Abdul I had the same issue I think Constant 500 error on Subflow, many flows stop working @abuaboud was able to fix it for me, maybe it’s related to the same issue?

We are self-hosted. I don’t think my links will work.

I read your thread and hoped to glean an answer, but it wasn’t posted… Hopefully, its something simple in my config, etc.

The update on the subflow is of last weekend I think, did you check for updates?

I’m on 39.2, it doesn’t show any other updates… unless there is a RC build?

Since I’m self-hosted, is it an issue with my environment settings? It looks like the SubFlow is essentially making an internal API call, so I’m wondering if it is a config issue. My webhooks work fine, though, and the sync returns also work.

@abuaboud would you be able to take a look as you resolved the previous issue I had too?

Are you self hosted @Bram ?

I am working in the cloud, but the issue seems the same as I had, Mo, which I tagged is the CTO, he fixed the issue for me in cloud, probably this is related.

Thank you for your help!

@Abdul Any ideas? I can’t get even simple sub-flows to trigger.

Hi there @Christian_DeRamos sorry for the delay, could you please duplicate your flows, remove all text that has acesstokens and the like, and export the duplicated flows to us ? that would help us a great deal in trying to fully understand the issue, also please try to run the flow and check the terminal for logs about the error, you should be able to see a more verbose error there which would also be helpful to understand the issue.