Issue Summary

After migrating a Slack workspace into a Slack Enterprise Grid (workspace consolidation/absorption), pre-migration users are unable to use the JSM Operations Slack integration. Attempting to create a new Slack integration or connect via the /connect slash command fails with a user ID mapping conflict error.

Steps to Reproduce

1. Have a Slack workspace connected to the OpsGenie/JSM Operations Slack integration with existing users linked.

1. Migrate that workspace into a Slack Enterprise Grid (workspace absorbed into Enterprise org).

1. Return to JSM Operations and attempt to create a new Slack integration, or use the /connect slash command in a Slack channel.

1. Observe the error when a pre-migration user attempts to authenticate or link.

Expected Results

Pre-migration users should be able to successfully authenticate and use the Slack integration after their workspace is migrated into a Slack Enterprise Grid. The system should reconcile old workspace user IDs with new Enterprise-assigned user IDs seamlessly.

Actual Results

The below exception is thrown

{"message":"A user entry exists with another slackUserId:[<enterprise_user_id>]","took":<time>,"requestId":"<request_id>"}  

The integration fails to map the user because the system already holds a record with the old workspace-level Slack user ID, and the new Enterprise Grid-assigned user ID is treated as a conflicting entry rather than an update to the existing mapping.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.