How these pages work
Every diagnosis here begins by making the fault visible, because automation fails silently and the first job is to find the record, the run or the field that shows it. A workflow problem starts with one test record walked through the platform's enrolment history; a data problem starts with the record's own history, which says who wrote the field and when; a reporting problem starts with the report grouped by the form, import or system that created the records. Once the fault is visible, a diagnosis table lists what you can see, the check that confirms each cause and the fix. Each cause then gets a short section with the fix, a way to verify it and the habit that prevents it, followed by a routine that keeps the whole set under watch between audits.
The pages assume the methods are taught elsewhere and link to them. The anatomy of a workflow, trigger, condition, action and exit, is in the workflows hub; the inventory, change log and safety rails are in the automation governance guide; the record's objects, source fields and merge rules are in the CRM fundamentals guide; and the contract between the CRM and a separate marketing platform is in the guide to syncing the two.
Find the page for your symptom
Choose the row that matches what you are seeing. Diagnosis pages in this section are also listed beneath this introduction automatically; the last three rows send faults that belong to another section to the page that owns them.
| What you are seeing | Start with | Background |
|---|---|---|
| A routing, assignment, field-update or alert workflow enrols nobody or acts on nothing | CRM workflow not running | Automation workflows |
| The merge queue refills every week with the same kinds of duplicate | Duplicate contacts in the CRM | Matching contacts to company records |
| A value someone corrected is back to the old one after the next sync | CRM values changing back after a sync | Data flow and integrations |
| Original source is blank, reads "import" or names the wrong campaign | CRM lead source blank or wrong | Campaign records in the CRM |
| Leads enter a nurture sequence and rarely reach its goal | Leads stalling in a nurture sequence | Lead scoring |
| An existing customer received a message written for prospects | Customers receiving prospect messages | Automation governance |
| A lead from a known account or territory reaches the wrong salesperson | Leads assigned to the wrong salesperson | Matching contacts to company records |
| Stages, next steps and close dates in the CRM are weeks out of date | Sales not updating the CRM | Weekly pipeline review |
| Customers tell support or social media that they hear from the business too often across email, texts and app messages | Customers getting too many marketing messages | Automation governance |
| An automated email never sends | Automated email flow not sending | Email automation |
| Sales is not following up the leads marketing hands over | Sales not following up on marketing leads | Lead stages and pipeline |
| Someone who unsubscribed is still receiving marketing email | Unsubscribed contacts still receiving email | Marketing opt-out request SOP |
Record, workflow or sync: decide which layer the fault lives in
Nearly every symptom in this section belongs to one of three layers, and deciding which one first saves most of the diagnosis. A record problem means the data the automation reads is wrong or missing: a field spelled several ways, a person held twice, a source never captured, a customer flag that was never set. A workflow problem means the record is right and the rule is wrong: a condition that no longer matches, an enrolment allowed once, a clone left running, a step pointing at a user who left, no exit on the goal. A sync problem means both the record and the rule are right in one system and wrong in the other: a field with two writers, a merge made on one side, a status that never crosses, a connector left on its defaults.
The test is to ask where the fact is true. If the CRM holds the right value and the marketing platform does not, the pillar's rule applies: the CRM is the system of record, and the integration that should have told the other system is what broke. If both systems agree and the workflow still does the wrong thing, read the rule as trigger, condition, action and exit. If the systems agree and the rule is sound but the value itself is wrong, the fault entered with the record, and the importing tutorial and the field standardising tutorial own most of the ways that happens. The ICO's direct marketing guidance matters in every layer for one class of record: a person who objected to marketing has to stay suppressed in every tool, so a sync, an import or a missing condition that lets them back in is a data protection matter as well as an automation one.
Problems that live inside one channel, such as an email flow that never sends or a platform's leads not reaching the CRM, belong on that channel's troubleshooting pages; the LinkedIn leads not syncing diagnosis is one example. This section covers what happens inside the CRM and the workflows that run on it.
When to audit instead
A diagnosis page fixes one fault. When several of these symptoms arrive together, when nobody can say what the workflows do or who owns them, or when the fields themselves have never been documented, an audit is the better tool. The lead management audit scorecard rates capture, routing, follow-up and reporting in one pass; the field audit tutorial lists every property, finds what writes and reads it and retires what nothing uses; and the governance guide sets the weekly, monthly and quarterly audit routine that catches most of these faults before a complaint does. The CRM section and the workflows section place the guides these pages draw on side by side.
