Start on the Connection page and click Test connection. A working connection shows Connected and the line Authenticated as, with the Pipedrive user and your company domain.
Not connected, or 401: the connection expired
Surge Dedupe refreshes its Pipedrive access on its own a few minutes before it expires, and tries once more if Pipedrive answers 401. If Pipedrive no longer accepts the refresh, for example after an uninstall or after access was revoked, the organization is marked as not connected.
- Open Connection.
- Click Reconnect with Pipedrive, or install again from the Pipedrive Marketplace.
- Allow access on the Pipedrive consent screen and finish the install screen.
- Back on Connection, click Test connection and check that it says Connected.
403, or merging is halted
A 403 means Pipedrive accepted the connection but refused the action. Surge Dedupe acts as the Pipedrive user who installed it, so that user needs permission to merge in Pipedrive. After 5 refused merges in a row, Surge Dedupe stops merging for your organization and the Review page shows Merging is halted. Syncing, searching, skipping and flipping keep working.
- On Connection, check which user is shown under Authenticated as. Surge Dedupe acts as that Pipedrive user.
- In Pipedrive, check that this user's permission set allows merging persons, organizations and deals, or reinstall Surge Dedupe while signed in as a user who may merge.
- Email info@sales-surge.nl to have the halt released. Releasing is a deliberate manual step, checked against the merge permission first, so the same failure does not start again.
429: Pipedrive rate limits
You do not need to do anything. When Pipedrive answers 429, Surge Dedupe waits as long as Pipedrive asks, up to about 20 seconds per call. If the limit lasts longer, the job keeps its position and continues on the next run a minute later. The merge log and error log show these as Pipedrive rate limit, marked as resolving on its own. Starting the job over only makes it slower.
A sync seems stuck
- Open the Dashboard and look at the Per-entity status table. A running job shows its progress, measured speed and remaining time.
- Background jobs move forward every minute. Click Run tick now to move them along straight away.
- Only one sync per record type runs at a time. Starting another one while a job runs only shows a message that it continues in the background.
- If the latest job failed, open Error log. Each entry says whether it Resumes on its own or Needs you, and what to do.
- If the error points to the connection, follow the steps for 401 above, then start an Incremental sync again.
Pipedrive does not know this record
The record was deleted or merged inside Pipedrive after the last sync. Run an Incremental sync so the copy in Surge Dedupe matches Pipedrive again, then handle the pair.
Still stuck? Email info@sales-surge.nl