Surface the raw platform response in syndication errors; soften 403 wording - #8
Merged
Merged
Conversation
…ording A target failure previously returned only a translated hint, so a 403 could not be diagnosed from the MCP surface (the tool returned the hint and an empty error record). Dev.to and Hashnode now include a one-line, length-capped slice of the platform's actual response body in the SyndicationError, so the raw Forem/Hashnode reason reaches the agent and the logs. The 403 wording is also softened: it no longer asserts the body/SVG as the cause (which misdirected a real diagnosis), and now reads "likely raw HTML/SVG in the post, or a key/permissions issue" with the raw response appended. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
A syndication failure previously returned only a translated hint, so a Dev.to/Hashnode 403 could not be diagnosed from the MCP surface (
blog_syndicate_postreturned the hint; the error record hadexternal_id: null). And the 403 wording asserted the body/SVG as the cause, which misdirected a real diagnosis.Changes
SyndicationError, so the raw Forem/Hashnode reason reaches the agent and the logs. (Hashnode's GraphQL-200-with-errorspath already surfaced the message; this covers the non-2xx path too.)Context
Read-only probes with the live key showed the SVG path is a dead end: the key is valid and can create articles, but all existing articles are drafts (
published: false) and our plugin sendspublished: true. The real 403 is almost certainly a publish gate / rate limit, not the body. This change makes the next retry self-diagnosing.🤖 Generated with Claude Code