OAuth token revoked during Slack app migration

Goal

Move a lightweight Slack app from one workspace to another while avoiding service interruption.

Constraints & Uncertainty

Slack’s migration guide requires reinstalling the app in the target workspace, which revokes the original OAuth token and forces a new token to be issued. Event subscriptions and slash‑command URLs are not automatically transferred; they must be manually re‑configured. It is unclear whether the app’s previously subscribed events (e.g., message events) remain active after reinstall or if they must be re‑subscribed each time. Real‑time connections (RTM or Socket Mode) will drop when the token is revoked, but the documentation does not specify how to detect this or reconnect gracefully without losing messages.

Unresolved Questions

• Does Slack automatically re‑subscribe to previously configured event types after a reinstall, or must the app perform a full re‑subscription?
• What is the recommended approach for detecting OAuth token revocation and reconnecting to Socket Mode or RTM to avoid downtime?
• Is there a documented pattern to minimize or eliminate downtime during the migration window, especially for high‑traffic apps?