Profiles Still Ingested After Disabling HTTP API Streaming Dataflow in AEP

Question

Hi All,I have configured an HTTP API streaming dataflow and successfully tested it using Postman-profiles are appearing in AEP as expected. However, I recently disabled the dataflow and then submitted another request via Postman. Surprisingly, the profile was still registered in AEP, even though the dataflow was disabled. Could someone help me understand how this is possible? Is there a delay in disabling the dataflow, or could there be another reason why profiles continue to be ingested?

bjoern__koth · Answer

Hi @amarapurammahesh,

when you disable an HTTP API dataflow in Adobe Experience Platform (AEP), the change should be effectively immediate and the dataflow will stop ingesting new data.

While the dataflow itself is disabled quickly, any data that was in transit or buffered before you disabled it may still be processed and ingested.

Can you still reproduce this behavior?

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded