Geography exclusions protect CRM data while retries hold up the rest of the workflow.
The run needs to preserve an auditable record of an exclusion without treating that exclusion like a recoverable failure.
Who you’d be doing this for
“My team keeps asking why a record we excluded is still holding up the whole run.”
Rafael Rojas · Revenue Operations Manager
Owns CRM data governance and waits on enrichment workflows before routing updated accounts to sales.
What is at stake
Excluded records are retrying and pushing 100,000-record workflow completion to 31 minutes. You must weigh faster completion against keeping every skipped record explainable in the run trace.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- faster workflow completion vs. auditable record outcomes
- shared Lambda capacity vs. broad retry recovery
- simple status handling vs. clear builder explanations
Why Clay
Workflows make high-volume enrichment usable only when every record has a clear outcome and active runs do not compete with avoidable retries.
Written with these in mind
Not your kind of problem? 15 more at Clay, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.