Skip to content

[Refactor] Centralize Fast inference attempt diagnostics - #1781

Draft
roomote-roomote[bot] wants to merge 2 commits into
developfrom
feature/fast-diagnostics-observability-13n5olblwi2vf
Draft

[Refactor] Centralize Fast inference attempt diagnostics#1781
roomote-roomote[bot] wants to merge 2 commits into
developfrom
feature/fast-diagnostics-observability-13n5olblwi2vf

Conversation

@roomote-roomote

Copy link
Copy Markdown
Contributor

​Created by Roomote. View the task or mention @roomote-roomote for follow-up asks.

What changed

  • Added one diagnostics-owned inference attempt API that records context submissions, provider retries, model and prompt milestones, outcomes, timing, and bounded failure logs.
  • Reduced the Fast turn service to execution and retry-policy callbacks instead of maintaining duplicate attempt counters, stage derivation, timing, and telemetry fan-out.
  • Added focused lifecycle coverage for success, provider recovery, setup and generation failures, clean retries, and side-effect recovery while retaining the existing telemetry schemas.

Why this change was made

Fast turn execution and turn diagnostics independently tracked the same inference lifecycle. Keeping those parallel state machines synchronized made context and retry observability harder to extend safely.

Impact

There is no intended user-facing behavior change. Fast inference diagnostics now have one owner, preserving privacy-safe telemetry and retry semantics while reducing orchestration inside the main turn service.

@roomote-community

roomote-community Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

No code issues found. See task

Reviewed f38c710

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