Reset Canvas State When Exiting Recent History in Sandboxes
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
When users open the “Recent History” modal in a Sandbox workflow and then close it, the canvas remains greyed out.
This creates confusion as it appears the editor is still inactive or loading.
A smoother transition and automatic state reset would improve usability.
Current Behaviour
- Opening the “Recent History” modal greys out the canvas (intended).
- After closing the modal, the canvas remains greyed out and unresponsive.
Expected Behaviour
When a user closes the “Recent History” modal:
- The canvas should automatically return to the active state.
- Users should be able to resume editing without needing a page refresh.
- The grey overlay should be removed regardless of the run status (Success, Exception, or Failed).
https://app.openfn.org/projects/88e66934-a572-495a-8891-546cc095e1e1/sandboxes
https://openfn.slack.com/archives/C0394D0GBUN/p1762770901493099?thread_ts=1762770023.444339&cid=C0394D0GBUN
Steps to Reproduce
- Navigate to a Sandbox workflow.
- Open the Recent History modal.
- View details of a run with status “Exception”.
- Close the modal.
- Observe that the canvas remains greyed out.
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
Reproduce the issue in a Sandbox workflow by opening Recent History, viewing an Exception run, and closing the modal. Trace the Recent History modal and canvas state transitions; done means the canvas is active and the grey overlay is removed after closing for Success, Exception, and Failed runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100