Hello,
I'm encountering a persistent issue when attempting to create a Dataflow in Adobe Experience Platform (AEP) via the Flow Service API.
### Problem Description
1. API Response: The API call to create the Dataflow consistently returns a `500 Internal Error` with the following details:
```json
{
"type": "https://ns.adobe.com/aep/errors/FLOW-1102-500",
"title": "Internal Error",
"status": 500,
"report": {
"detailed-message": "An internal error has occurred. Please try again. If the problem persists, please contact customer support.",
"request-id": "jRYpviErjYYlp5lIszoHrfdtUb3pQZ3B"
},
"errorMessage": "An internal error has occurred. Please try again. If the problem persists, please contact customer support.",
"errorDetails": "An internal error has occurred. Please try again. If the problem persists, please contact customer support."
}
```
2. UI State: Despite the API error, the Dataflow is created and visible in the AEP UI. However, it remains perpetually in the 'Processing' state (or similar initial creation state) and has not transitioned to 'Active' or 'Failed'.
3. Duration: The Dataflow has been stuck in this 'Processing' state for **over 15 hours**.
4. Prerequisites Status: The prerequisite components (Source Connection, Target Connection, and Mapping Set) were all successfully created via their respective APIs and received successful responses.
I have tried creating the Dataflow twice, resulting in the same API error and subsequent stuck 'Processing' state in the UI for both attempts.
Has anyone experienced this specific combination of an API-side `500 Internal Error` leading to a UI-side Dataflow stuck in 'Processing'?
What could be the underlying reason for this issue, given that all dependencies seem correct? Could this indicate a configuration problem that the API fails to handle gracefully, or is it likely a backend service issue?
Any guidance or troubleshooting suggestions would be greatly appreciated\!
Thank you.
