When uploading lead lists to Salesforce with the intent of assigning them to specific sales reps, PaperTube encountered a persistent issue where leads were being distributed randomly via the Super Round Robin flow — even when the "do not add to Super Round Robin" field was explicitly set to false. This article documents the root cause and the technical workaround developed by Asymmetric's Salesforce specialist.
Related client: [1]
Related campaign: [2]
Leads uploaded via CSV with the Super Round Robin exclusion field set to false were still being assigned randomly across the sales team rather than to the designated rep specified in the Lead Owner ID column.
The expected behavior — direct assignment to a specific rep — was not occurring despite the field being correctly populated.
Multiple active Salesforce flows are running simultaneously for the Super Round Robin assignment logic. When a lead is uploaded, these flows execute in sequence and override the custom field value set during import. The exclusion field is effectively negated before the assignment logic completes.
"There's multiple flows that Super Round Robin has on, and even though there's some customizations of if this is true, then don't add it to the Super Round Robin flow — since there's a couple flows running, it's negating that field."
— Karly Oykhman, summarizing the specialist's findings
This is a known complexity in orgs where multiple automation layers (flows, process builders, or triggers) interact with the same record fields on creation.
Asymmetric's Salesforce specialist identified a technical workaround that bypasses the conflicting flows during lead upload. The exact implementation details were to be documented and sent to Parag Agrawal separately.
Previous manual workaround (pre-fix): Temporarily disable the round robin feature entirely, upload the leads, then re-enable it. Functional but operationally disruptive.
Status as of 2026-01-22: Specialist was actively testing the fix. A summary was to be sent to PaperTube once confirmed.
The Asymmetric team profile does not have full visibility into all Salesforce flows in PaperTube's org. This limitation is acceptable for lead uploads but would become a blocker if the work expanded to uploading accounts or contacts, which would require elevated permissions.
This issue is not unique to PaperTube. In any Salesforce org with multiple active flows touching lead assignment, field-level overrides set during import can be silently negated. When troubleshooting unexpected round robin behavior:
See also: [3] (stub — create if pattern recurs)