Expand my Community achievements bar.

Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are adopting AI into their workflows securely, responsibly, and at scale.

Profiles Still Ingested After Disabling HTTP API Streaming Dataflow in AEP

Avatar

Level 2

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?

7 Replies

Avatar

Community Advisor

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? 

Cheers from Switzerland!


Avatar

Level 2

Hi @bjoern__koth ,

Yes, I tried again just now, and profiles are still being registered in AEP.

 

Thanks ,

Mahesh 

 

Avatar

Community Advisor

Maybe open a support ticket in that case

Cheers from Switzerland!


Avatar

Level 2

I got the below response from Adobe.

 

Disabling the dataflow alone will not guarantee that ingestions are prevented. Since AEP auto create system dataflows if the target dataset is enabled for profile, data may still come in.

Avatar

Level 3

@AmarapuramMahesh ,

 

Did you manage to solve this issue? Thanks!

Avatar

Level 2

Hi @Abie ,

This issue is still ongoing. Despite deleting the dataflow and submitting the request from Postman, profiles are still being registered in Adobe Experience Platform (AEP).Based on the response from Adobe, we have parked the issue for now.

Avatar

Level 3

Hi @AmarapuramMahesh ,

 

I think you could solve this by limiting the write permissions on this particular dataset. If the given access token isn't authorized to write on this dataset, the requests will be unauthorized or failed batch ingestions. You might want to try that?

 

Thanks!