@Michael_Soprano I believe in this case, your HTTP Streaming REST API dataflow is created on top of the same underlying streaming engine / connection spec that also powers the Azure Event Hubs connector. I assume these two are using the same target dataset? If you generate a new dataflow (either Eve...

Correct, although we don’t expose a specific “X characters max” limit in official guardrails, some destinations have their own limits on the concatenated name/id they receive. Adobe Campaign has a ~250‑character composite limit for audience name + id + destination name/id

If the segment was created recently, there could be some timing issue whereby it wasn't included in the latest batch daily segment job but the fact you see 0 seems to indicate the system did not compute anything for that definition.  Recommendation here is to raise a Support ticket so the teams can ...

@Pradeep-Jaiswal I don't believe individual profile/fragment size is currently exposed. The size of the Profile store can be seen in the Preview sample status endpoint: GET https://platform.adobe.io/data/core/ups/previewsamplestatus  That would give you the overall size as well as the fragment count...

@Michael_Soprano you want to chek if a file copied to the DLZ correctly?You should be able to list the files with azcopy, something like:azcopy list "<containerURL>"   If on the other hand, you want to monitor if AEP actually ingested the data from the DLZ, the AEP UI monitoring is probably the best...

@SouravBh5 Difficult to answer fully, in theory you could see sample profiles because the sample job once captured profiles that matched some prior segment logic (+ sample jobs do not usually update every day), while the current audience evaluation might legitimately have 0 qualified profiles.   Has...

@SantoshRa5 as far as I can see, segment evaluation method (batch / streaming / edge) is part of the segment definition metadata (evaluationInfo) held by Segmentation Service, not by UPS snapshot datasets.   Using a segmentation API filter will narrow down to batch-only segments GET https://platform...

@sheejo  I just tried with: GET https://platform.adobe.io/data/foundation/flowservice/flows/:ID to get the original details of the flow   Then used: PATCH https://platform.adobe.io/data/foundation/flowservice/flows/:ID   .. with the following body (which is your original attempt):   [ { "op": "repl...

@Michael_Soprano monitoring will help focus on the numbers but an easier way is to check the dataflow runs for said destinations, if records failed or were skipped, it is likely you will get some sort of messaging / error codes in there. For some of them it is pretty self-explanatory, for others, yo...

I believe the inletID is at Account level, it is not needed this if you want to create a dataflow: https://experienceleague.adobe.com/en/docs/experience-platform/sources/api-tutorials/create/streaming/http#create-a-dataflow