Fact 271
QA confirmed by January 14, 2026 that Mercury’s OAuth-cancel path tells users authorization was canceled before Scaffold connected the source, says no data was synced, and provides a clear `Try again` path when connector context can be preserved; providers that do not preserve connector context fall back to the generic source picker on the first pass.
Source evidence (1)
002566Jan 14, 2026 / 12:52 UTC-08:00
Closing the loop: Priya and Jake shipped the January Mercury OAuth-cancel activation fix. Production deploy is done, and QA confirmed the cancel path now tells the user authorization was canceled before Scaffold connected the source, says no data was synced, and gives a clear `Try again` path when connector context can be preserved. For providers that don’t preserve connector context, the first pass falls back to the generic source picker. QA also confirmed the successful OAuth callback path is untouched — workspace creation, source connection, and first live sync still pass. No admin-role work, granular-role scope, SAML change, or growth-proof instrumentation shipped.
Message 002566 in history