---
title: Salesforce Round-Robin Bypass — PaperTube List Upload Troubleshooting
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
- papertube
- list-upload
- troubleshooting
- flows
- csv-import
- escalation
layer: 2
client_source: Paper Tube Co
industry_context: ecommerce
transferable: false
---

## Overview

Mark Hope and Karly Oykhman worked through a Salesforce CSV list upload for PaperTube, attempting to prevent the "Round Robin Lead Assignment" flow from firing and reassigning imported leads away from Karly. Two bypass methods were applied simultaneously; both failed. The 5 test leads were reassigned to another user, manually corrected, and the issue was flagged for re-testing and potential escalation to Demetri.

**Attendees:** Mark Hope, Karly Oykhman
**Client:** PaperTube
**Date:** 2026-04-05

---

## The Problem

PaperTube's Salesforce org has a flow called **"Round Robin Lead Assignment"** that triggers automatically on new lead creation. When importing a list via the Data Import Wizard, this flow fires and reassigns leads away from the intended owner (Karly), defeating the purpose of the manual upload.

### Flow Trigger Conditions (AND logic — both must be true to fire)

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

Because both conditions must be met, setting the exclude field to `TRUE` *should* prevent the flow from firing. The `Lead ID` condition is always true for new imports, so the exclude field is the only lever available.

---

## Bypass Methods Attempted

Two methods were applied together during the test upload:

### Method 1 — CSV Field: `DEP_Exclude_from_Round_Robin_Assignments__c`

- Added a column to the import CSV with the API field name `DEP_Exclude_from_Round_Robin_Assignments__c`
- Set the value to `TRUE` for all rows
- Mapped the column during the import wizard field-mapping step

### Method 2 — Import Wizard: Assignment Rule & Round-Robin Recipient

During the Data Import Wizard setup screen:
- **Assign All Leads Using the Assignment Rule:** set to `None`
- **Round Robin Recipient:** set to `None`

Both options were explicitly set to `None` in addition to the CSV field approach.

---

## Test Results — Both Methods Failed

A test batch of **5 leads** was uploaded with both bypass methods active.

**Result:** The Round Robin Lead Assignment flow still triggered. All 5 leads were reassigned to another user.

Karly manually reassigned all 5 leads back to herself. Because the batch was small, no lasting damage was done — this is a key reason to always test with a small batch before a full upload.

---

## Other Setup Completed During This Session

- **Lead Source field:** Added `"Asymmetric"` as a new picklist value to the `Lead Source` field so that leads from Asymmetric-sourced lists are properly attributed.
- **CSV format confirmed:** Import file is a CSV with column headers matching Salesforce API field names.
- **New custom fields:** NAICS code and other fields were created in Salesforce and mapped in the CSV prior to this session.
- **Owner field:** Must match the exact full name as it appears in Salesforce (not just a first name).

---

## Key Decisions

- Always test with a small batch (3–5 leads) before running a full list import — catches both field mapping errors and flow interference without causing widespread reassignment.
- If the bypass cannot be resolved internally, escalate to **Demetri** with a clear description of what was attempted and what happened.

---

## Action Items

- [ ] **Karly** — Reassign the 5 test leads back to herself (completed during session)
- [ ] **Karly** — Re-run the import with a fresh 5-lead batch using the same bypass methods (DEP_Exclude = TRUE, Assignment Rule = None, Round Robin Recipient = None)
- [ ] **Karly** — If leads are reassigned again, escalate to **Demetri** with: what was attempted, the flow name ("Round Robin Lead Assignment"), and the result

---

## Escalation Path

**Escalate to:** Demetri
**Trigger:** Round-robin bypass fails on re-test
**Include in escalation:**
- Flow name: `Round Robin Lead Assignment`
- Bypass methods already tried (both CSV field and import wizard `None` selections)
- Evidence: leads were reassigned despite `DEP_Exclude_from_Round_Robin_Assignments__c = TRUE`

---

## Related

- [[clients/current/papertube/_index]]
- [[knowledge/salesforce/csv-list-import-best-practices]]
- [[knowledge/salesforce/flow-troubleshooting]]