INSIGHTS
AI & Automation Insights for Operators
Practical guides on AI assistants, workflow automation, lead intelligence, and field operations. Written for business owners and operators who want results, not hype.
Deleted records don't sync, then they come back
A sync misses deletions because polling asks which records changed since a timestamp, and a deleted record is not returned by any query, so the delete is an absence rather than a change. Even after you detect it, propagating a hard delete removes the destination row that was holding your deduplication key, so the next update from the source finds no match and re-creates the record. The durable fix is the tombstone pattern databases use: sync an active flag and a deleted-at timestamp, and never remove the row.
Automation running twice? It is overlapping itself
A scheduled automation processes the same record twice when the next run starts before the previous one has written back its result, which happens whenever run duration approaches the schedule interval. Platform settings that promise one run at a time are throttles rather than locks: n8n's concurrency limit applies to the whole instance, Make's sequential processing halts on any unresolved incomplete execution, and Zapier documents that its queue delay does not guarantee steps never run simultaneously. The reliable fix is to claim each record with a status write before doing the work, so an overlapping run finds nothing left to take.
Opt-Outs Don't Sync Across Your Tools
Opt-outs stop only the tool that received them, because every messaging platform, CRM, and email system keeps its own consent flag and none of them tell the others. Federal rules give you ten business days from the moment a request is made in any reasonable manner, including phrasings your vendor's keyword parser never sees, so the fix is one consent record of record that fans out to every sender rather than a set of per-tool flags that drift.
Large files break automations. Pass links, not bytes
Automations fail on large files because every step that materializes the file holds its own copy, in memory and then in the retained execution record, and base64 encoding inflates each copy by about a third. The fix is to upload the file to storage once and pass a URL or object key between steps so exactly one step ever holds the bytes. Airtable's own API shows the size of the difference: the same attachment field accepts 5 MB when you send the file bytes directly and 5 GB when you send a link.
Matching customer records without a shared ID
An automation should link a record across two systems only on exact normalized keys: a stored cross-reference ID, a lowercased email, or a phone in E.164 format. Everything that merely looks similar goes to a human review queue. The reason is asymmetry, not accuracy: HubSpot states that records cannot be unmerged, so a false merge is permanent, while a false split costs one manual merge.
Webhooks arriving out of order? Fix the write, not the sort
Webhooks arrive out of order because sources like Stripe and Shopify document that they do not guarantee delivery order, and because automation platforms run webhook-triggered executions concurrently, so two runs for the same record can finish in the wrong sequence. Sorting by timestamp only addresses the first cause. The reliable fix is to treat the webhook as a signal, re-fetch the record from the source API, and guard the write with a per-record watermark so a late run cannot overwrite newer data.
Your automation only synced the first 100 records
An automation that syncs only the first batch of records is usually missing pagination, but the failure that survives correct pagination is offset paging over data that is being written to, which both skips and duplicates rows. Because a partial sync exits cleanly and reports success, the only reliable detector is comparing the source count against the destination count on every run.
Automated Texts Not Delivering? Count Segments, Not Sends
Automated text messages usually fail on carrier limits that are counted in message segments per registered business, shared across every phone number, campaign, and platform under the same EIN. Buying more numbers adds no capacity, and a single non-ASCII character in an AI-written message body cuts the segment size from 160 characters to 70, tripling what one reminder consumes.
Two-way sync keeps overwriting your good data
A two-way sync overwrites good data because the sync's own write updates the last-modified timestamp it uses to decide who wins, so the receiving system looks newer on the next pass. The fix is to assign every synced field to one owning system and run two one-way syncs over field sets that do not overlap, instead of one bidirectional sync with a conflict rule.
Automated Emails Going to Spam? Check the From Domain
Automated emails usually land in spam because of the domain they were sent from, not the copy inside them. Gmail and Microsoft both apply bulk-sender authentication rules per From: domain at 5,000 messages a day, and both treat crossing that line as permanent, so a nurture sequence that shares a domain with your invoices drags the invoices into the same reputation.
Why Your Automation Ran an Hour Off, and What It Missed
A scheduled automation drifts by an hour for two different reasons, and only one of them is a setting you can fix in five minutes. The harder failure is that a daylight saving day runs 23 or 25 hours, so a step that looks back exactly 24 hours on a fixed daily schedule double-processes an hour of records every March and skips an hour every November, with no error in the run log either time.
Why Your Automation Keeps Asking You to Reconnect
Automation connections break for four reasons, and the refresh token lifetime a vendor advertises is rarely one of them. The two that actually bite are a rotating refresh token your side failed to save, and an automation that runs too rarely to keep its token alive. Both are fixed by design choices made before the connection dies, not by clicking reconnect again.
Want a system like the ones we write about?
We build practical AI and automation systems for businesses that need better workflows, connected tools, and cleaner operations.
Request a Workflow Review