fix: include response body in scheduler client error on non-200 status - #1113
Open
cortex-ai-agents[bot] wants to merge 1 commit into
Open
fix: include response body in scheduler client error on non-200 status#1113cortex-ai-agents[bot] wants to merge 1 commit into
cortex-ai-agents[bot] wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
cortex-ai-agents
Bot
requested review from
PhilippMatthes,
SoWieMarkus,
juliusclausnitzer,
mblos and
umswmayj
as code owners
August 3, 2026 07:20
Contributor
Test Coverage ReportTest Coverage 📊: 70.4% |
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.
When the external scheduler returns a non-200 status code, the ScheduleReservation method in SchedulerClient discards the response body and only reports the status code. PR #1104 enhanced the server-side scheduler to return useful error details in its response body on 500, but the client never reads that body, making the improvement invisible to operators debugging failover scheduling failures.
This change reads the response body (with a 1024-byte size limit to avoid OOM on pathological responses), logs it, and includes it in the returned error message. This closes the debuggability gap so operators can see the actual error details from the scheduler without needing to correlate server-side logs.
Assisted-by: Claude Opus 4.7 (claude.ai)