Answer: You must trigger a full restart of the provisioning cycle, since an incremental sync will not update existing records after changing an attribute mapping. In PingOne, trigger a full provisioning cycle in the app's provisioning settings (you may need to disable and re-enable provisioning); in PingFederate, trigger a full sync in your outbound provisioning channel. Status: Confirmed Entry: tool/claude-apps/troubleshooting/trigger-full-resync-ping-identity Revision: 3 Digest: sha256:c2aec7c309146d56 (changes whenever the content changes) Timeline: Created: 2026-11-13T02:59:05Z Last changed: 2026-11-20T12:05:20Z (Verification: — → Verify that updated email values appear in provisioning logs) Last verified: 2026-11-20T12:05:20Z Next check: 2026-11-21T12:05:20Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Sync type required | Full sync required | [1] | 2026-11-20 Required action | trigger a full restart of the provisioning cycle | [1] | 2026-11-20 PingOne action | trigger a full provisioning cycle | [1] | 2026-11-20 PingOne fallback | disable and re-enable provisioning | [1] | 2026-11-20 PingFederate action | Trigger a full sync in your outbound provisioning channel | [1] | 2026-11-20 Verification | Verify that updated email values appear in provisioning logs | [1] | 2026-11-20 Sources: [1] Anthropic. "Ping Identity SSO/SCIM email mismatch | Claude Help Center". https://support.claude.com/en/articles/13917875-ping-identity-sso-scim-email-mismatch Role: primary. Accessed: 2026-11-20T12:05:20Z Quote: "Critical — Full sync required: An incremental sync will not update existing records after you change an attribute mapping." (Supports: Sync type required) Quote: "You must trigger a full restart of the provisioning cycle." (Supports: Required action) Quote: "PingOne: In the app's provisioning settings, trigger a full provisioning cycle." (Supports: PingOne action) Quote: "You may need to disable and re-enable provisioning to force a complete re-push." (Supports: PingOne fallback) Quote: "PingFederate: Trigger a full sync in your outbound provisioning channel." (Supports: PingFederate action) Quote: "Verify that updated email values appear in provisioning logs before asking people to retry login." (Supports: Verification) Snapshot SHA-256: 4a42516b4b3abd70a7c184074a8f9ff153435b93f65310c540b196d985733d21 (captured 2026-11-19T12:01:49Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-19T12:01:51Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:05:20Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:05:20Z Last attempt: 2026-11-20T12:05:20Z Notes and limitations: Extracted automatically from a single official source (section "Trigger a full re-sync"). Related: https://latestn.com/tool/claude-apps/troubleshooting/unhelpful-prompt-answers Why isn't Claude giving me helpful answers to my prompts? https://latestn.com/tool/claude-apps/troubleshooting/users-cannot-update Why can't users update Claude Desktop and how do I fix it? https://latestn.com/tool/claude-apps/troubleshooting/verification-failed What happens if my identity verification on Claude fails? https://latestn.com/tool/claude-apps/troubleshooting/suspicious-activity-after-revoking-key What should I do if I still see suspicious activity after revoking my Claude API key? https://latestn.com/tool/claude-apps/troubleshooting/tenant-restrictions-error-responses What error responses occur with Claude Tenant Restrictions and how do I fix them? https://latestn.com/tool/claude-apps/troubleshooting/test-deep-link How do I test a claude:// deep link on macOS, Windows, or Linux? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:05:20Z | changed | Verification: — → Verify that updated email values appear in provisioning logs | [1] 2026-11-20T12:05:20Z | changed | Required action: — → trigger a full restart of the provisioning cycle | [1] 2026-11-20T12:05:20Z | changed | Sync type required: — → Full sync required | [1] 2026-11-20T12:05:20Z | changed | incremental sync limitation: An incremental sync will not update existing records after you change an attribute mapping → — | [1] 2026-11-20T12:05:20Z | changed | sync type required: full restart of the provisioning cycle → — | [1] 2026-11-17T12:07:17Z | changed | incremental sync limitation: — → An incremental sync will not update existing records after you change an attribute mapping | [1] 2026-11-17T12:07:17Z | changed | PingOne fallback: — → disable and re-enable provisioning | [1] 2026-11-17T12:07:17Z | changed | sync type required: — → full restart of the provisioning cycle | [1] 2026-11-17T12:07:17Z | changed | Verification step: Check your provisioning logs → — | [1] 2026-11-17T12:07:17Z | changed | PingOne force option: disable and re-enable provisioning → — | [1] 2026-11-17T12:07:17Z | changed | Required sync type: full restart of the provisioning cycle → — | [1] 2026-11-13T02:59:05Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-apps/troubleshooting/trigger-full-resync-ping-identity/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-apps/troubleshooting/trigger-full-resync-ping-identity POST: https://latestn.com/dispute/tool/claude-apps/troubleshooting/trigger-full-resync-ping-identity with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-apps/troubleshooting/trigger-full-resync-ping-identity?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I trigger a full re-sync after fixing a Ping Identity email mismatch in Claude? Revision 3, last verified 2026-11-20T12:05:20Z. https://latestn.com/tool/claude-apps/troubleshooting/trigger-full-resync-ping-identity (accessed 2026-11-21T10:02:17Z). @misc{LatestN_tool_claude_apps_troubleshooting_trigger_full_resync_ping_identity_r3, title = {How do I trigger a full re-sync after fixing a Ping Identity email mismatch in Claude?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-apps/troubleshooting/trigger-full-resync-ping-identity}}, note = {Revision 3; digest sha256:c2aec7c309146d56; last verified 2026-11-20T12:05:20Z; accessed 2026-11-21T10:02:17Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-apps/troubleshooting/trigger-full-resync-ping-identity