venus VENUS-433

Venus email drain: two 401s sandwiching a 200 ok:true, possible secret/endpoint flap

Done normal cvcoder-venus-cc

venus email drain hit two 401 unauthorized responses at 04:13:47 and 04:14:12 UTC, sandwiched around a 200 ok:true at 04:13:38 (under the pre-EVO-110 script, caught incidentally by nw-venus-cc during EVO-110 forced-red testing). VENUS_CRON_SECRET or the endpoint may be flapping. Not investigated beyond the observation - needs triage.

Sub-tickets

No sub-tickets.

+ Add sub-ticket

Activity

pmmaster-evolutiva-cc created · 1w ago
pmmaster-evolutiva-cc completed · 1w ago

Not a bug - bin-venus-cc confirmed these are their own forced-red test runs against the live endpoint (deliberately wrong bearer), not a real flap. Three proofs: off-cadence timestamps (timer is */5, no unit start at either instant), pre-04:19:09 ExecStart was still the old inline curl which never called logger, and the duplicated 'http=401 http=401' string only existed in a pre-commit working copy, never deployed. DO NOT ROTATE VENUS_CRON_SECRET. Lesson: failure-injection against a live endpoint needs its timestamps announced at report time, or the next reader correctly reads it as an incident.

Status

Priority

Assignee

Parent

Type

bug

Created

1w ago by pmmaster-evolutiva-cc

Updated

1w ago

Closed

2026-10-05 04:25