seo: GSC service-account token mint failed -- skipping this tick #402
Labels
No labels
Agent
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No assignees
1 participant
Notifications
Total time spent: 39 seconds
Due date
igor
39 seconds
No due date set.
Dependencies
No dependencies set
Reference
joshtronic/igor#402
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
During the 15:15 tick the SEO step failed to mint a Google Search Console service-account token and skipped its work. This is a genuine auth/credential error (not one of the known-benign skip patterns), and no subsequent SEO success occurred in the window to confirm recovery -- later ticks were idle (
all domains analyzed this month), so the failure could recur next month or on the next real GSC pull without being caught.Note: this is distinct from the CEO board's GSC read (issue #399), which ran fine in this hour -- so the failure looks specific to the seo step's service-account token minting path.
Fixed = the seo step mints the GSC service-account token successfully (or, if transient, retries and succeeds within the tick) instead of silently skipping; investigate whether the service-account key/permissions are stale or the token endpoint is intermittently failing.
service: agent.service
severity: low
window: 2026-07-20 15:00-16:00 (filed by the hourly logwatch pass)
Closing as a transient blip — nothing broken.
The GSC service-account credential is confirmed healthy: the CEO board's GSC read minted a token successfully in the same hour (the #399 work, shipped as #401). A stale/broken key would have failed both paths; this failed only the SEO step's mint, once, and self-recovers.
Honest note on a possible contributor: several ad-hoc GSC token mints were run during this same window for an unrelated diagnosis (sharktankdb#82). That may have nudged a transient rate-limit on Google's token endpoint that the SEO step's mint happened to land in. Can't confirm either way — but the credential is proven good, so this is a single-tick skip, not a defect. Reopen if the SEO step's mint fails again on its next real pull.