Skip to content

Make failed destination recovery explicit - #325

Merged
Ankit6149 merged 2 commits into
masterfrom
feat/connector-truth-batch
Sep 25, 2026
Merged

Ankit6149 merged 2 commits into
masterfrom
feat/connector-truth-batch

Conversation

@Ankit6149

Copy link
Copy Markdown
Owner

Advances #29 without claiming the whole issue complete.

Implemented:

  • failed destinations render an explicit "Generation failed" recovery state
  • failed/needs-review issues use an alert role for assistive technology
  • the active failed destination action is labeled "Retry destination"
  • retry continues through the existing CHANNEL regeneration policy, which targets exactly the active destination and preserves unrelated drafts
  • regression coverage pins isolated retry targeting and failed-state recovery UI

Not complete:

  • queued/generating/revising/cancelled live statuses
  • save/reopen acceptance specifically for failed retry transitions
  • full keyboard/screen-reader acceptance pass

@vercel

vercel Bot commented Sep 21, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
signal-flow-studio Ignored Ignored Sep 21, 2026 8:49pm UTC

@Ankit6149
Ankit6149 merged commit d0a0fd3 into master Sep 25, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant