Skip to content

Isolate thread sharing failures from other work - #361

Merged
vinayagg merged 1 commit into
mainfrom
codex/isolate-thread-sync-failures
Nov 6, 2026
Merged

vinayagg merged 1 commit into
mainfrom
codex/isolate-thread-sync-failures

Conversation

@vinayagg

@vinayagg vinayagg commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

What broke
An incomplete organization setup or a failed thread registration or metadata update could prevent unrelated saved conversations from loading. Some unrelated permission errors were also shown as revoked thread access.

Why
Refreshing the directory attempted to sync every locally owned thread and stopped at the first failure. Reads depended on that refresh, so one document's failure affected other work.

What changed

  • Keep registration and metadata failures on the affected thread or team and continue syncing other work.
  • Defer automatic sharing when organization access cannot be verified and retry on subsequent refreshes.
  • Show sharing notices for the selected thread or team and preserve specific permission errors.
  • Add regression coverage for failure isolation, recovery, access revocation, and notice visibility.

Tested
npm run check passed on the final branch, including client regressions, TypeScript checks, and desktop and hosted UI builds. Native installer packaging and manual UI testing were not run.

@vinayagg
vinayagg merged commit 10d1cf5 into main Nov 6, 2026
2 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