Skip to content

Commit a27f2b0

Browse files
pc-styleclaude
andcommitted
fix(server): abort deletion cleanup when the thread lookup fails
A failed projection read now propagates to the worker's logging catch instead of defaulting to the destructive path. The idle-session reaper backstops any cleanup this skips. Co-Authored-By: Claude Fable 5 <[email protected]>
1 parent 4e3cada commit a27f2b0

1 file changed

Lines changed: 1 addition & 3 deletions

File tree

‎apps/server/src/orchestration/Layers/ThreadDeletionReactor.ts‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -72,9 +72,7 @@ const make = Effect.gen(function* () {
7272
event: ThreadDeletedEvent,
7373
) {
7474
const { threadId } = event.payload;
75-
const thread = yield* projectionThreadRepository
76-
.getById({ threadId })
77-
.pipe(Effect.orElseSucceed(() => Option.none<ProjectionThread>()));
75+
const thread = yield* projectionThreadRepository.getById({ threadId });
7876
if (shouldSkipThreadDeletionCleanup(thread)) {
7977
yield* Effect.logDebug("thread deletion cleanup skipped a re-created thread", { threadId });
8078
return;

0 commit comments

Comments
 (0)