eds wf app delete: 500 with an empty body for applications in "error" #25

Problem

Applications left in error by failed eds wf app create calls (during a Workflow Studio outage) cannot be removed.

Steps

1. eds wf app list --space-id <space> shows several applications with status: error.
2. eds wf app delete <id> --force → Error: workflow client delete application: 500 Internal Server Error. Reproduced on 5 of 5 such applications in a row (2026-11-01, 14:19–14:22 MSK).
3. A direct DELETE /workflow/v1/project/{project}/application/{id} returns HTTP 500 with the body {}.

Also

• Their pipelines stay as well, and eds wf pipeline has only list and show, so there is no way to clean them up from the CLI.
• For one older application, eds wf app show <id> reports status: deleted, while eds wf app list --space-id <space> still lists it with status: error.

Expected

eds wf app delete removes an application in any state together with its pipeline, or returns a 4xx that explains why it can't.

The x-request-id values of the failed calls can be shared privately.

Environment: eds main-868af1c, macOS.