Meta Conversions API returns 400 after working for two days

If your server-side events fire correctly for a day or two and then start failing with HTTP 400, the payload shape is almost never the problem. Something that changes on a timer is.

The five causes, in order of likelihood

CauseWhat you seeFix
Access token expired or permissions changed400 with an OAuth error / code 190Use a system-user token with no expiry, stored in a credential, not inline in a module
Test event code left in the live pathEvents land in Test Events, or the call rejects itStrip test_event_code from production, keep it in a separate branch
event_time in the wrong unit or window"invalid event_time"Unix seconds, not milliseconds; not in the future; not older than 7 days
Missing action_source"action_source required"Every event needs it: website, physical_store or system_generated
Unhashed or malformed user_data"user_data invalid"Lowercase, trim, SHA-256 the email and phone; send fbp/fbc when present

Why it breaks on a timer, not on deploy

A token that expires, a batch that grows past the request limit, or a retry loop that starts double-counting are all quiet until they are not. The scheduler keeps running, the workflow keeps reporting success, and the only signal is a 400 body nobody reads.

What a hardened setup looks like

Broken right now? Send the failing response body and I will tell you which of the five it is. Fixed fee for the repair, and if events are not accepted you do not pay.

perun.intelligence@gmail.com — n8n and Make automation builds.