Question Re: SAP DRC Cloud (ECC) in Technology Q&A

SAP DRC Cloud (ECC)

SoniaFletcher — Tue, 10 Feb 2026 16:57:25 GMT

Hi,

We have implemented the latest version for KSeF version 3. I'm getting this new error message has anyone come across it?

The exchange of electronic documents or report submission failed while executing the IFLOW_HTTP_COMMAND action because of an unexpected error in the process orchestration

The error message actually instructs user to try and submit again "Compliance, cloud edition. Try again in a few minutes, and if the error persists, open a support request. Find the relevant app", but when we try we get an error message in the bottom left of the screen "The action is not allowed for any of the selected eDocuments".

I'm also not sure what this means;

{"source":"/default/sap.s4.gco.edoc/gpeclnt500","processInstances":[{"id":"000D3ADDB9461FE180CC540FE3BAE37E","processType":"CUSTOMER_INVOICE","processSubtype":"B2B","processVersion":"1.0.0","countryRegion":"PL","status":"RECEIVED","followupRequired":"","followupActions":"","documents":[],"messages":[]}]}

Initially I wondered if it was an authorisation issue with the "The action is not allowed for any of the selected eDocuments" error BUT I have logged on with extensive authorisation and still get the same error. Any help advice appreciated.

Many thanks

Sonia

Re: SAP DRC Cloud (ECC)

amontella96 — Thu, 12 Feb 2026 01:18:26 GMT

hi @SoniaFletcher there is literally no trace of an IFLOW_HTTP_COMMAND error so i must ask where did you get that ? can you post some details like how did you configure in soamanager /default/sap.s4.gco.edoc/gpeclnt500

Re: SAP DRC Cloud (ECC)

abisha_s — Tue, 17 Feb 2026 08:08:09 GMT

Hi - I am facing the same error in 'Resolve errors' app in DRC cloud application. Did you find the solution?

Re: SAP DRC Cloud (ECC)

NiclasBo — Tue, 17 Feb 2026 09:14:17 GMT

Hi, we are also facing this issue. Hoping for a solution soon.

Re: SAP DRC Cloud (ECC)

magnusrudenielsen — Wed, 18 Feb 2026 09:45:44 GMT

TLDR: Change service plan to Test and make sure Communication setting is configured correctly
We experienced the same issue, but have just resolved the issue.
We had a mismatch of our DRC Service Plan/Communication Setting.
We wanted to set up a Test-system to send Customer Invoices from the business system through DRC, where we encountered the IFLOW_HTTP_COMMAND error. When we encountered the error, we had the service plan, Standard, and had set our Communication Settings to Test.
We resolved it by changing the DRC service plan to Test aswell, which ultimately led to us being able to getting an approval from KSeF. However, currently we still experience some 403-error on the DRC error log.