Include DataForSEO status code in AI Overview errors#473
Merged
Conversation
The AI Overview failure path threw only DataForSEO's status_message ("Internal SE Server Error."), hiding the numeric status_code that distinguishes a billing/limit rejection from a genuinely transient server error. Match the LLM Responses path and prefix the code, so a failing scheduled run is self-diagnosing.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Why
The
/statuspage shows 0% for Google AI Overview on DataForSEO. Diagnosis so far: in a single CI run, every DataForSEO surface passes (AI Mode + ChatGPT/Perplexity/Gemini LLM Responses) except Google AI Overview — the only one usinggoogleOrganicLiveAdvanced+load_async_ai_overview— which fails 100% withInternal SE Server Error. The same request succeeds 10/10 against a different (demo) DataForSEO account. That points at an account-level difference on DataForSEO's side (async-AI-Overview feature enablement, balance, or a cost cap on the extra async charge), not a code bug.The blocker to confirming this is that the failure path threw only DataForSEO's
status_message("Internal SE Server Error."), swallowing the numericstatus_code. The code distinguishes a billing/limit rejection from a genuinely transient server error.Change
Prefix the DataForSEO
status_codeto the AI Overview error, matching what the LLM Responses path already does. The next failing scheduled run then logs e.g.DataForSEO API Error: 40202 ...instead of an opaque message — self-diagnosing the real cause.Follows #472 (the retry). Internal error-detail only — no changeset.