Handle deleted workflows/projects gracefully
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
If you have a sandbox workflow open in one tab and you delete the sandbox project by merging on separate tab (or someone else does the merge), you'll end up with 500s in your page.
These are the sentry errors that you would get: https://openfn.sentry.io/issues/7432737142/events/2e39f4373b46483b92090ea5ade83bad/
https://openfn.sentry.io/issues/7365481289/events/60795b20aa4345fd97bab4b8a07a9b24/
How can we improve the ux?
Suggestions are to broadcast a message when the project is deleted
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the sandbox workflow/project deletion scenario described in the issue and review the two linked Sentry errors. Define a graceful user experience for an open page after its project is deleted, then verify that the scenario no longer produces 500 errors.
Written by the indexing model from the issue text.
Assessment
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100