Alright, let's add another entry to my ever-growing list of "Why I Switched" documentation. This time, it's Runway's turn under the microscope.
I’m in Year One of my Runway experiment, having migrated off Salesforce (don't ask) last quarter. The sales team's number one request was a dead-simple email-to-task system: sales rep BCCs a specific address, it lands as a task on the relevant contact/company, no fuss. In theory, it's a baseline feature for any modern CRM. In practice, Runway seems to be interpreting "create a task" as "create three or four tasks, because why not?"
Here’s the symptom: A rep BCC's the magic inbox on a customer email. About 70% of the time, it works. The other 30%, we get duplicate—and sometimes triplicate—tasks. They're identical in every field: same subject, same contact link, same notes. It's not a slight delay causing a second send; they appear in the activity feed simultaneously.
What I've ruled out so far:
* **User error:** It's a single BCC, not multiple. We've trained this out of teams three CRMs ago.
* **Forwarding rules:** No one is using Gmail's "Forward and BCC" or similar nonsense. It's a direct BCC from the original thread.
* **Simple duplication in the task list view:** These are genuinely separate task objects with unique IDs. Closing one leaves the others open.
My suspicion is landing in one of two places, based on scars from previous platforms:
1. **Runway's email parsing engine** is triggering multiple times on a single incoming email. Maybe it's scanning the header, finding the thread, and creating a task for each recognizable "participant" in some flawed logic? Or it's firing both on the original *and* on some internal automated receipt?
2. **An integration conflict.** We have the Google Workspace sync enabled (obviously). Could there be a handshake where Google says "got it" and Runway's listener, not getting an immediate 'ack,' tries again? I've seen similar behavior in other systems where the webhook fires more than once.
The fallout is the usual: reps get annoyed, stop trusting the automation, and start manually logging. Then the data gets spotty, forecasting goes out the window, and my phone rings with "why is our CRM crap?" questions. I'd rather head this off.
Has anyone else deconstructed this particular glitch? I'm about to start combing through activity logs and maybe even setting up a dedicated mailbox with more verbose forwarding to trace the incoming signal. Before I go down that rabbit hole, I'm curious if the community has already found the smoking gun in a setting I've missed. Is the "Email-to-Task" feature just fundamentally janky, or is there a specific config tweak that stabilizes it?