A successful save still needs a working form
On November 8, I corrected the final step of shortlist creation in Seasonal.Work. The request could succeed, yet the interface could still report an error while trying to reset the form afterward. The problem was in the handoff between submitting the form and handling the later response, rather than in the shortlist information itself.
The submission handler originally reached back through the event to find the form after waiting for the request. By that point, the event no longer provided the form in the way the handler expected. I kept a reference to the submitted form before starting the asynchronous operation and used that reference when resetting it after success. The change left the request and the surrounding workflow intact.
The visible sequence matters as much as the final confirmation. While creation is pending, the title, expiry, notes and candidate selection should remain visible, and the saving action should not invite a second submission. After success, the form can clear, the selection can return to zero and the list can refresh to show the new report. Clearing everything too early would make a delayed or failed operation harder to understand; failing after success would make a completed operation look uncertain.
I added a case that deliberately delays the successful response so those two phases can be checked separately. It follows the submitted values, the disabled saving state, the eventual reset and the refreshed list, while checking that only one write occurs. The November 8 correction was integrated with the broader workspace presentation changes on November 10. The specific lesson comes from the save sequence, not from the size of that later integration.
Reflection
In Seasonal.Work, the form needed to survive long enough to finish its own workflow. Keeping the submitted element available made the interface's success path match the completed operation without adding another request or another layer of state management.