digest stale-open nudge reports on RFIs whose live fetch always fails — Procore RFI detail decode error (15/24h) #15
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?
Problem
The digest task's stale-open nudge is reporting against RFIs it cannot fetch live. Every fetch fails with a body-decode error, and the design deliberately proceeds on the stale local copy:
Observed 2026-11-02 (last 24h window, tenant
gal, project 361980):procore decode error: rfi detail: error decoding response bodystale-open nudge sent count=16procore 429 — backing off(unrelated, normal rate limiting)Why it matters
The nudge path intentionally fails soft — "keeping (nudge, don't suppress)" — because silently dropping a stale item is worse than nudging on possibly-stale data. That trade is defensible for an occasional failure. It is not defensible as a permanent steady state: if every live fetch fails, the digest is nudging people about the state of 16 RFIs using local data that may no longer match Procore.
The decode failure is on the RFI detail endpoint (
GET /rest/v1.0/projects/{id}/rfis/{rfi_id}shape), not the list endpoint. Most likely a Procore API response-shape change: a field added as an incompatible type, a null where a value was expected, or a renamed key. The 429s are incidental and not the cause.What to find out
rfi_idand diff it against the struct the app deserializes into. The error iserror decoding response body— serde's message with detail would name the field; the current log line drops it.Scope note
Nothing is submitted to Procore by this path — the nudge is an internal digest notification. This is a data-fidelity and diagnostics defect, not a write-safety one.
Verification
procore decode errorcount returns to 0 andstale-open nudgestill sends for genuinely stale items.