SynapCores v1.14.5 — Your agent wasn't broken. It never got the event.
The report that started this was four words long: "it stopped firing."
Someone had a durable agent bound to a table:
CREATE AGENT churn_watcher
PERSONA 'analyst'
TASK 'Assess the account and record your finding.'
ON INSERT INTO churn_signals;
It worked when they tested it. It worked the next morning. Then, under real traffic, it started missing rows — not erroring, not logging, not retrying. Just not running.
The measurement
Same agent, same table, same INSERT. The only variable was whether the engine happened to be busy:
| user INSERT lands | binding fires? |
|---|---|
| engine idle | yes — every time |
| during an agent run | no — never |
Not flaky. Deterministic, in the worst possible direction: it worked in testing and failed in production, because testing is quiet and production is not.
Why
An agent's own writes must not re-fire event bindings. Otherwise an agent with write access whose INSERT matches its own trigger becomes an infinite, billable loop. So the engine tags writes made inside an agent run and skips bindings for them. That part is correct and necessary.
The problem was where the tag lived: a single process-wide flag, held for the entire duration of the run.
An agent run is dominated by waiting on a language model. Two seconds against a hosted API. Forty-five to a hundred and eighty seconds on a CPU-only host — which is what Community Edition ships as. For that whole window, every write in the process looked like it came from the agent. Your user's INSERT. Your webhook's INSERT. Everything.
The worse your hardware, the more events you lost. And nothing was logged, because from the engine's point of view nothing had gone wrong — it was doing exactly what it was told.
The fix
Write provenance is now per-task. It follows the statement that actually made the write, across await points and thread migration, and is carried explicitly across the internal boundary where the database spawns its write work.
The old process-global is still there, deliberately, as a backstop for any path that loses the marker. That asymmetry is the whole safety argument: a user write mistaken for the agent's only misses a firing, and you can re-run it. An agent write mistaken for a user's re-fires the agent's own binding, and that bills you until you notice.
Verified by running the same test against both binaries on live gateways, with the in-flight window confirmed open on both sides of the commit:
v1.14.4 (before) idle 2/2 fired in-flight 0/2 SUPPRESSED
v1.14.5 (after) idle 2/2 fired in-flight 2/2 BOTH fired
There is also a new runaway guard: more than 120 event fires per agent per minute are refused and reported. Far above anything the runtime can actually process — it exists to bound the damage if provenance is ever wrong on some path nobody has walked yet.