Running Activate
Partner reconciliation
The issues raised when PartnerStack partners do not match the registry, and how each one is resolved.
Partner reconciliation
When a synced PartnerStack partner cannot be safely matched to the Activate partner registry, Activate raises a reconciliation issue instead of guessing. Issues are listed at Partners > Partner reconciliation in the client portal, and in the mirror at /admin/activate/mirror/{engagement}/partners/reconciliation.
The issue types
| Issue | Recommended resolution |
|---|---|
| Provider name is missing | Correct the name in PartnerStack and retry, or link to a known partner |
| Category is outside the captured Strategy baseline | Create the partner without that category, link it to an existing partner, or correct the category and retry |
| Partner name could not be matched safely | Choose the existing partner that owns this PartnerStack identity, or correct the data and retry |
| Provider identity belongs to another engagement | Check the PartnerStack tenant and credentials, then retry |
| Partner name and provider identity disagree | Confirm the correct partner and link it, or correct the provider record and retry |
Each card shows what happened, the recommended resolution, the matched partner (if any), the region and when the issue was first observed.
The actions
| Action | Effect |
|---|---|
| Create partner | Creates the partner and resolves the issue (category issues only) |
| Link partner | Links the PartnerStack identity to an existing registry partner |
| Retry sync | Queues a verified PartnerStack reconcile |
| Ignore issue | Closes it without change. Use only when the record is meant to be out of scope. |
Filter by Open, Resolved, Ignored or All. With nothing open, the page reads "PartnerStack and the canonical partner registry are currently reconciled."
Who resolves them
The client resolves issues in their portal. The mirror is read-only here ("Open the client portal to resolve, ignore, or retry an issue."). Your job is to spot open issues and guide the client. Where the fix belongs in PartnerStack, the client's PartnerStack admin makes it, then retries.