Routine log: 2026-07-09 daily-cron health — IG still stuck, PR #151 unmerged#152
Draft
neverpeakev wants to merge 1 commit into
Draft
Routine log: 2026-07-09 daily-cron health — IG still stuck, PR #151 unmerged#152neverpeakev wants to merge 1 commit into
neverpeakev wants to merge 1 commit into
Conversation
…unmerged Today's FB post is healthy (gen-2026-07-09-f455k, fb_published_at 14:02:08 UTC). IG mirror cron fired at 14:15:08 UTC, returned 200, wrote nothing. Same failure as every day since 2026-05-27 — fetchPageContext throws, the current catch block returns without console.error or markFailed, so 44 consecutive days are invisible in both Vercel logs and the DB. The fix already exists as PR #151 (branch claude/fix-content-cron-2026-07-08), opened yesterday, still draft/open/unmerged. Not opening a duplicate — the log just flags the merge as the single unblocking action, and lists the Meta-token rotation the PR body already teed up. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014fMwsDdBVPnqY8rP2KvgNB
|
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
2 participants
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.
Summary
Daily supervision run for 2026-07-09. FB post published cleanly at 14:02:08 UTC; IG mirror is still silently failing (44th consecutive day since 2026-05-27) because PR #151 — the diagnosed fix — is still open/draft/unmerged.
gen-2026-07-09-f455k, anglegymnastics-viewing-window-leotard-rec, display "She named the leotard / through the viewing window.", fb_post_id1086292991223812_122116529234989743.ig_published_atstill null,error_messagestill null.listPendingIgMirrorbacklog now sits at 43 rows.fetchPageContextthrows (almost certainly the Meta scope regression identified in PR Fix daily content cron: IG mirror silently failing since 2026-05-27 #151), the current catch block returns{ok:false}withoutconsole.errorormarkFailed, so nothing surfaces. Merging PR Fix daily content cron: IG mirror silently failing since 2026-05-27 #151 makes the next cron flip today's + backlog rows toig_failedwith the real Meta error inerror_message, at which point the token can be rotated with the right scopes.Not opening a duplicate fix PR — PR #151 already contains the exact code change needed.
Test plan
generated_postsfor today: one row,status=fb_published,ig_published_at=null./api/social/ig-mirror 200with no stderr — matches the diagnosed silent-catch path.ig_failed.META_MARKETING_API_TOKENwithinstagram_basic+instagram_content_publishscopes.ig_publishedwith a realig_media_id.Generated by Claude Code