Hosted relay ghost workflow cannot be deleted

[wjbright]

Summary

A workflow in a hosted Buzz community is no longer visible in Buzz Desktop, but the relay still returns it and the scheduler continues to run it. Deletion is reported as accepted without removing the workflow.

Affected community

• Community: zairaa.communities.buzz.xyz
• Workflow ID: 86cf70ff-d8f8-4c04-8b29-c4f81907777b
• Workflow name: Cross-board control pulse
• Buzz Desktop: 0.4.26

Observed behaviour

1. The Desktop Workflows screen shows no workflows.
2. Relay/CLI workflow lookup still returns the workflow definition.
3. A delete request returns accepted: true.
4. Subsequent workflow list/get checks still return the workflow.
5. The hosted scheduler continues to execute it.

Expected behaviour

Deleting the workflow should remove or disable both the relay definition and its scheduler state. A deletion whose backend side effect fails should not be reported as successfully accepted without an actionable error.

Operator action requested

Please urgently disable or delete this workflow in the hosted relay backend and verify that no enabled scheduler entry remains for the workflow ID above.

Please also investigate the inconsistent state and the false-success deletion response so an owner can recover from this condition through the normal Desktop/CLI flow.

[crsmoore]

We hit a closely related state on another hosted *.communities.buzz.xyz community: workflows delete returned accepted: true (three attempts) while list/get kept returning the workflow. In our case a workflows trigger probe returned 400: workflow not found — meaning the delete had actually worked and the workflow can no longer run; what was left behind was only its stored definition record (the kind:30620 event), a "ghost" listing for a workflow that no longer exists. That's the #2879 behavior (full details in my comment there: #2879 (comment)). But until we ran that probe, the symptoms were indistinguishable from what's described here.

If the scheduler in your case is genuinely still firing the deleted workflow, that's a worse variant than #2879 covers. +1 for operator tooling on hosted relays to verify (and force-remove) scheduler state for a given workflow ID.