Launch blocker: fix multi-create provisioning modal overlap/confusion #10

New Issue

jester · 2026-05-02T23:39:13Z

jester commented

2026-05-02 23:39:13 +00:00

Launch blocker / launch UX bug

Portal currently allows creating multiple servers at the same time. Both servers create, but the provisioning/setup modals overlap/replace each other: the first modal goes away and the second remains visible. This is confusing and could make users think the first create failed or disappeared.

Current observed behavior

User can submit multiple server creations concurrently.
Both servers are actually created.
The provisioning modal/state for the first server is overtaken by the second.
Only the second provisioning modal remains visible.

Desired behavior options

Pick one launch-safe approach:

Single-create lock
- Disable additional create actions while a server creation is in progress.
- Show clear text that setup is already running.
Multi-create queue/list
- Allow multiple concurrent creates but show them as separate setup cards/progress rows on the Servers page.
- Avoid modal stacking or global singleton modal state.
Redirect-only setup tracking
- After submit, close modal and rely on server-list provisioning cards for all in-progress creates.
- No global modal should be able to hide another in-progress server.

Validation needed

Start two server creates quickly and confirm UI remains understandable.
Confirm both server provisioning states remain visible or one create is intentionally blocked.
Confirm no maximum update-depth/state hydration loop regresses.
Confirm success/failure/toast behavior maps to the correct server.

Launch expectation

This is not a backend provisioning failure, but it is launch-blocking UX confusion for first-time users.

## Launch blocker / launch UX bug Portal currently allows creating multiple servers at the same time. Both servers create, but the provisioning/setup modals overlap/replace each other: the first modal goes away and the second remains visible. This is confusing and could make users think the first create failed or disappeared. ## Current observed behavior - User can submit multiple server creations concurrently. - Both servers are actually created. - The provisioning modal/state for the first server is overtaken by the second. - Only the second provisioning modal remains visible. ## Desired behavior options Pick one launch-safe approach: 1. **Single-create lock** - Disable additional create actions while a server creation is in progress. - Show clear text that setup is already running. 2. **Multi-create queue/list** - Allow multiple concurrent creates but show them as separate setup cards/progress rows on the Servers page. - Avoid modal stacking or global singleton modal state. 3. **Redirect-only setup tracking** - After submit, close modal and rely on server-list provisioning cards for all in-progress creates. - No global modal should be able to hide another in-progress server. ## Validation needed - Start two server creates quickly and confirm UI remains understandable. - Confirm both server provisioning states remain visible or one create is intentionally blocked. - Confirm no maximum update-depth/state hydration loop regresses. - Confirm success/failure/toast behavior maps to the correct server. ## Launch expectation This is not a backend provisioning failure, but it is launch-blocking UX confusion for first-time users.

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: jester/zlh-grind#10