---
title: Round-Robin Lead Assignment Flow — Bypass Methods
type: article
created: '2026-04-05'
updated: '2026-04-05'
source_docs:
- raw/2026-01-20-list-upload-papertube-sf-115704295.md
tags:
- salesforce
- round-robin
- lead-assignment
- flows
- csv-import
- troubleshooting
layer: 2
client_source: null
industry_context: null
transferable: true
---

# Round-Robin Lead Assignment Flow — Bypass Methods

## Overview

Salesforce's "Round Robin Lead Assignment" flow automatically reassigns newly created leads to a rotating queue of users. This is problematic during manual list uploads, where leads need to be assigned to a specific owner. Two bypass methods exist in theory; both were tested during a [[clients/papertube/_index|PaperTube]] list upload and **both failed** — the flow fired anyway. The issue was escalated to Demetri for investigation.

---

## Flow Trigger Conditions

The flow is named **"Round Robin Lead Assignment"** and triggers on **record creation** (new lead). It fires only when **all** of the following conditions are met (AND logic):

| Condition | Value |
|---|---|
| `DEP_Exclude_from_Round_Robin_Assignments__c` | `FALSE` |
| `Lead ID` | `NULL` (i.e., the record is new) |

Because both conditions must be true simultaneously, setting the exclude field to `TRUE` *should* prevent the flow from firing.

---

## Bypass Method 1 — CSV Field

Add a column to the import CSV with the API field name and set it to `TRUE` for all rows.

**Field API name:** `DEP_Exclude_from_Round_Robin_Assignments__c`

**Steps:**
1. Open the import CSV.
2. Add a new column with the header exactly matching the API field name above.
3. Set the value to `TRUE` for every row (all caps recommended for reliability).
4. Save the file as CSV before importing.

**Rationale:** If the field is `TRUE` at the moment of record creation, the flow's first condition is not met and it should not fire.

---

## Bypass Method 2 — Import Wizard Selections

During the Salesforce Data Import Wizard, explicitly opt out of assignment rules.

**Steps:**
1. In the import wizard, locate the **"Assign leads using the assignment rule"** dropdown.
2. Select **None**.
3. Locate the **"Round Robin recipient"** dropdown.
4. Select **None**.
5. Proceed with the import.

**Rationale:** Selecting None for both options should prevent the wizard from invoking any assignment logic.

---

## Test Results (PaperTube, 2026-01)

Both methods were applied simultaneously during a 5-lead test upload:

- DEP Exclude field set to `TRUE` in the CSV ✓
- Import wizard: Assignment Rule = None, Round Robin Recipient = None ✓

**Result: FAILED.** The flow triggered regardless, reassigning all 5 leads to another user. Karly manually reassigned the leads back to herself.

> "We said none and none, and then we also said true — we even went the extra step — and I don't know why it triggered." — Mark Hope

---

## Other Import Setup Notes

- **File format:** CSV with column headers matching Salesforce API field names exactly.
- **Owner field:** Must match the full display name of the user in Salesforce (not just first name).
- **Lead Source:** A new picklist value `"Asymmetric"` was added to the `Lead Source` field to properly attribute leads sourced by Asymmetric. This should be selected in the import wizard's source dropdown rather than mapped as a CSV column (the wizard pre-fills it, removing it from the field mapping step).
- **Test batch size:** Always run a 3–5 lead test import before uploading the full list. This limits reassignment damage and surfaces field mapping errors early.

---

## Status & Next Steps

- [ ] Karly to re-run the 5-lead import with both bypass methods applied.
- [ ] If the flow fires again, escalate to **Demetri** with a description of what was attempted and what happened.

The root cause is unknown. Possible explanations include a timing issue (flow evaluates field value before the CSV column is committed), a secondary flow or trigger not yet identified, or a misconfiguration in how the import wizard interacts with record-triggered flows.

---

## Related

- [[clients/papertube/_index|PaperTube]]
- [[meetings/2026-04-05-papertube-sf-list-upload-troubleshooting|Meeting: PaperTube SF List Upload Troubleshooting]]