Workflows recover better when something fails.
This release makes everyday product work more forgiving. Saves, imports, generation steps, and navigation paths across Discovery, initiatives, products, settings, and connected tools now keep more context visible when something needs a retry.
What changed
- Failed saves and generation steps keep more of the user's work available for retry
- Discovery, initiative, and product navigation paths recover more consistently
- Teams transcript scans can stay partially usable when one part fails
- Connected-tool setup and OAuth callback routes handle edge cases more clearly
Recovery paths are clearer across daily workflows
Several save, import, and generation flows now preserve more local context and expose clearer retry paths. The focus is simple: when a network request, provider call, or generation step fails, the user should not have to recreate work they already entered.
- Settings, product, initiative, and Discovery edits are easier to retry
- Failed AI-assisted steps leave clearer next actions
- Users spend less time rebuilding interrupted work
Navigation and source review stay better connected
Discovery overview links, product knowledge review routes, related idea links, initiative document routes, and existing entity references now resolve more predictably. Teams transcript imports also keep useful partial scan results available instead of treating every partial issue as a dead end.
- Source links and related records are easier to follow from review surfaces
- Partial Teams transcript scans still give teams something useful to inspect
- Connected-tool permission and callback flows fail with clearer boundaries
More in this release
Recovery and retry polish
Interrupted workflows are easier to resume.
- Settings, product, initiative, backlog, context, feedback, and admin actions keep clearer retry paths
- AI-assisted generation and planning flows surface recoverable failures more consistently
- Manual and connected imports preserve more context after failed actions
Navigation and connected-tool reliability
Review routes and integration boundaries are steadier.
- Discovery overview taxonomy links open the expected table views
- Existing ideas, insights, and opportunities can show their external References links
- Product knowledge, related idea, and initiative document routes recover more reliably
- Teams transcript scans can keep partial results available
- OAuth metadata, consent, and callback routes handle boundary cases more clearly