Conversation
Every row rendered Unavailable for two independent reasons: the insight fetch asked PostHog for `refresh: 'force_cache'`, which never recomputes, so a stale or short cache failed the complete-28-day-window check; and any insight carrying a breakdown was refused outright, which covers 9 of the 13 managed insights. The fetch now asks for `refresh: 'blocking'`, which serves a fresh cache and otherwise recalculates synchronously. If PostHog still answers with a pending query_status, we re-read the cache a bounded number of times and leave the row Unavailable rather than hanging or printing a zero. Breakdown insights are no longer refused. Because breakdown_limit means PostHog returns only the top N values, summing them would undercount, so we re-issue the insight's own trends query with the breakdown stripped and label the row "total across all breakdown values". Every existing refusal that protects correctness is unchanged: non-trends insights, non-daily intervals, non-additive math, and short or undated result series still render Unavailable with their current reasons. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
blove
enabled auto-merge (squash)
September 18, 2026 18:38
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
This branch was successfully deployed
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.
Every row of the generated weekly GTM report read
Unavailable.Two causes: the insight fetch used
refresh: force_cache, which never recomputes a stale cache, and breakdown insights (9 of 13 managed insights) were refused outright.refresh: blocking(serve fresh cache, otherwise recalculate synchronously), with a bounded poll if PostHog answers with a pendingquery_status. Never hangs, never prints a zero it cannot stand behind.Verified against live PostHog: every row in all three dashboards now carries a real number.
🤖 Generated with Claude Code