Arnas Donauskas 635b5c1df6 fix(automations): atomic execution_count via SQL function (migration 007) ... The engine did a client-side read-modify-write on automations.execution_count, so two concurrent dispatches of the same automation (e.g. fired for two different contacts within the same second) could both read N and both write N+1, permanently losing one count. - Migration 007 adds increment_automation_execution_count(p_automation_id) as a SECURITY DEFINER sql function. Only service_role can EXECUTE it — an authenticated user can't juice someone else's counter by calling the RPC directly. - Engine now calls this RPC instead of reading automation.execution_count and adding 1. Atomic in one statement; concurrent dispatches both land correctly. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-17 21:45:27 +03:00
..
001_initial_schema.sql	fix: make migration idempotent	2026-04-16 19:46:41 +03:00
002_pipelines_enhancements.sql	feat(pipelines): Kanban drag-drop, analytics, deal sheet, contact deals tab	2026-04-16 22:38:45 +03:00
003_broadcast_recipient_wamid.sql	fix(broadcasts): per-recipient variables, webhook status sync, rate limit	2026-04-17 11:22:38 +03:00
004_contact_delete_set_null.sql	fix(contacts): allow deletion — SET NULL on broadcast_recipients, deals	2026-04-17 16:56:45 +03:00
005_broadcast_counts_incremental.sql	fix(broadcasts): senior-review hardening pass	2026-04-17 17:38:52 +03:00
006_automations.sql	feat(automations): visual flow builder, engine, and logs viewer	2026-04-17 19:39:02 +03:00
007_automations_increment_counter.sql	fix(automations): atomic execution_count via SQL function (migration 007)	2026-04-17 21:45:27 +03:00