fix(telemetry): close recovered task lifecycles - #277
Closed
IRONICBo wants to merge 1 commit into
Closed
Conversation
|
@IRONICBo is attempting to deploy a commit to the socai Team on Vercel. A member of the Team first needs to authorize it. |
This was referenced Aug 31, 2026
Collaborator
Author
|
Closing per maintainer request to keep the active delivery queue focused on four PRs only: audio/video integration, Douyin, TikTok, and the consolidated browser self-healing PR #292. This PR remains available in history and can be restored separately if needed. |
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
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.
Summary
Evidence
The sanitized seven-day Axiom export for v0.5.5 contains two macOS task IDs with one start and no end, plus one Windows task ID with two starts and one end. The persisted task registry already converts leftover running tasks to interrupted at startup, but that recovery path did not emit the matching terminal telemetry event.
This change is prospective. It closes future recovered lifecycles; it cannot backfill historical gaps that were already persisted as interrupted.
Verification