# Catch a sync failure between your systems before it runs for weeks > Regular spot checks and one place to report oddities catch partial sync failures early, and every gap gets reconciled. Markdown view of https://www.tabflows.com/university/playbooks/integration-sync-failures — the HTML page is canonical. [](https://www.tabflows.com/university/playbooks) 1. [Playbooks](https://www.tabflows.com/university/playbooks) 2. [Practice Admin](https://www.tabflows.com/university/playbooks#practice-admin) Regular spot checks and one place to report oddities catch partial sync failures early, and every gap gets reconciled. - Tabflows Last checked Oct 27, 2026 against Tabflows v3.10.63 ## The situation An integration between two of your systems, the EHR feeding billing or scheduling syncing with messaging, usually works quietly. The dangerous failure is not a total break, which someone notices fast. It is a partial one: most records keep syncing, a few quietly do not, and nothing looks broken. Nobody's job is to check that integrations still work, so the first sign is a problem downstream. A charge never reaches billing, a record is missing recent updates, a message never triggered its task. By then the sync may have been failing for days or weeks. ## Steps 1. **Schedule a spot check** Create a Task for one owner and set Repeat to a regular schedule, such as Weekly or Monthly. Each time, pick a handful of recent records and confirm each one matches in every system it should have synced to. 2. **Watch new connections closely** When a new integration goes live, give it its own spot-check Task that comes back more often for its first few weeks. New connections are the likeliest to have edge cases or setup problems. 3. **Give staff one place to report oddities** Anyone who sees a record that looks incomplete or a charge that is not where it should be creates a Task for the owner with the patient attached, and, where the patient is linked there, Tag to system set to the system where it showed up. They do not need to be sure it is a sync problem, because these one-off oddities are often the first real signal. 4. **Scope it and call the vendor** When a failure is confirmed, add a comment with what was affected and since when. Contact the vendor or IT support right away, and set the Task to Waiting while they work on it. 5. **Reconcile what was missed** Add a checklist item for each record that did not transfer during the failure, fix each one by hand, and keep the Task open until every item is checked. ## The outcome Partial failures get caught early instead of weeks later, staff observations reach someone who looks into them, and every failure ends with the missing data reconciled, not just the sync fixed going forward. **Important ⚠️:** A fixed sync works going forward only. It does not backfill what failed to transfer during the failure window, so that gap stays until someone reconciles it. ## Ask Sidekick Sidekick is the AI assistant inside Tabflows. Hey Tabflows, create an urgent task for this sync problem with the systems involved, the records affected and what looks wrong, assigned to our office admin. ## In the Product Library - [Keep tasks clear with due dates, urgency, and task details](https://www.tabflows.com/university/library/tasks/keep-tasks-clear-with-due-dates-urgency-and-task-details) - [How to update, complete, reopen, or delete tasks](https://www.tabflows.com/university/library/tasks/how-to-update-complete-reopen-or-delete-tasks) - [Break larger tasks into subtasks](https://www.tabflows.com/university/library/tasks/break-larger-tasks-into-subtasks) - [Collaborate on tasks with comments and mentions](https://www.tabflows.com/university/library/tasks/collaborate-on-tasks-with-comments-and-mentions) [Read the full guide](https://www.tabflows.com/blog/integration-sync-failure-monitoring) ## Related markdown Section index: [Playbooks](https://www.tabflows.com/university/playbooks.md) Alongside this page: - [Advance directive tracking](https://www.tabflows.com/university/playbooks/advance-directive-tracking.md) - [After hours answering service](https://www.tabflows.com/university/playbooks/after-hours-answering-service.md) - [After hours message triage](https://www.tabflows.com/university/playbooks/after-hours-message-triage.md) - [Billing decline follow up](https://www.tabflows.com/university/playbooks/billing-decline-follow-up.md) - [Call follow up loop](https://www.tabflows.com/university/playbooks/call-follow-up-loop.md) - [Chronic care check ins](https://www.tabflows.com/university/playbooks/chronic-care-check-ins.md) - [Clia and compliance renewals](https://www.tabflows.com/university/playbooks/clia-and-compliance-renewals.md) - [Dea and license renewals](https://www.tabflows.com/university/playbooks/dea-and-license-renewals.md) Start here: - [Tabflows](https://www.tabflows.com/index.md) - [Tabflows pricing](https://www.tabflows.com/pricing.md) - [Tabflows FAQ](https://www.tabflows.com/faqs.md) - [About Tabflows](https://www.tabflows.com/about.md) - [Contact Tabflows](https://www.tabflows.com/contact.md) - [DPC workflow software](https://www.tabflows.com/dpc-workflow-software.md) - [Directory](https://www.tabflows.com/directory.md) - [Workflows](https://www.tabflows.com/workflows.md) - [DPC finder](https://www.tabflows.com/dpc-finder.md) Every page listed in sitemap.xml has a markdown twin at the same URL with `.md` appended, or by sending `Accept: text/markdown` to the canonical URL. Wider index: [llms.txt](https://www.tabflows.com/llms.txt), [llms-full.txt](https://www.tabflows.com/llms-full.txt), [sitemap.md](https://www.tabflows.com/sitemap.md), [sitemap.xml](https://www.tabflows.com/sitemap.xml). Support documentation: https://www.tabflows.com/university/library — append `.md` to any article URL for its raw markdown.