fix: show actionable release activation errors (MCP-16) - #56
Merged
Merged
Conversation
Cover backend error details, metadata review, pending retries, active status refresh, cache invalidation, and release/project isolation so failed activations stay actionable.
Surface server activation errors in accessible row alerts, clear stale errors on retry, and guide readiness failures into MCP metadata review. Reset local state across project navigation while preserving successful activation cache refreshes.
Exercise a deferred metadata lookup through project navigation so an old release cannot reopen dialogs or write deep-link state after its project unmounts.
Prevent a delayed metadata lookup from opening a stale dialog or replacing the new project's URL after the release table unmounts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem and change
When release activation is rejected, the dashboard currently leaves the release unchanged without explaining why. The affected row now displays the backend error in an accessible alert. Readiness failures offer Review MCP Metadata, and retry clears the stale message before submitting again.
Errors are isolated by release and project. Delayed metadata lookups discard navigation and dialog changes after leaving a project. Existing activation cache invalidation and backend readiness checks are preserved.
Validation
Frontend-only; no migration or backend behavior change. Development deployment and authenticated acceptance follow CI/merge. Production promotion requires separate approval.
Refs MCP-16.