What happened?
After completing a provider login flow, the user is not redirected to the relevant connection page. This makes the flow feel incomplete and forces the user to manually navigate to confirm or manage the new connection.
What did you expect?
After a successful login, the UI should redirect to the connection detail page for the provider/connection that was just created or updated. The user should land somewhere that confirms the connection exists and allows them to inspect or manage it.
Steps to reproduce
- Start the app locally.
- Run or trigger a provider login flow, for example GitHub.
- Complete the OAuth flow successfully.
- Observe the post-login redirect behavior.
- Update the flow so success redirects to the corresponding connection page.
What happened?
After completing a provider login flow, the user is not redirected to the relevant connection page. This makes the flow feel incomplete and forces the user to manually navigate to confirm or manage the new connection.
What did you expect?
After a successful login, the UI should redirect to the connection detail page for the provider/connection that was just created or updated. The user should land somewhere that confirms the connection exists and allows them to inspect or manage it.
Steps to reproduce