Why is the Close Button (X) Non-Functional in Pipedream Connect Auth?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

hi, we are having issues when trying to close the auth in pipedream connect using the ‘X’.

We confirmed that the data was properly flowing through our system into pipedream. The close button (X) is still non-functional, and investigation into the HTML served makes it appear that the close button just doesn’t do anything.

2

I submitted a support issue under the title Connect Link "Close (X)" button non-functional on Pipedream-hosted connect page or something close to it.

Very possible we have a bug in our system, but things seem to look good from my end.

3

Are you using the frontend SDK or Connect Link?

4

Connect link

5

What would you expect that close button to functionally do in that context?

6

Either:

  1. Receive a cancel_redirect_uri to customize cancelling behavior
  2. Return to previous window if possible
  3. Just not see the close button
  4. Return to a base url
7

Yea I think #3 makes the most sense to me. I agree that seems like a bug in that context, will look into it.

8

I appreciate it!

If it were up to me, I would push for the first option. A cancel_redirect_uri seems to fit the current shape of the API and makes things a bit more customizable from our side. I wouldn’t expect it to be a huge lift with your current patterns, but I have never looked at your code and have almost no context on the inner workings of your systems!

Three makes sense as well!

Thanks!

9

I have a patch for #3 ready to go, it was a 1-liner :slightly_smiling_face:

10

Will let you know when it’s out

11

FYI this is out in production

CleanShot 2025-12-15 at 14.21.28.png
CleanShot 2025-12-15 at 14.21.28.png417×616 26.7 KB

12

Thanks so much!

Is there any possibility of having the cancel_redirect_uri request to come through the pipeline eventually?

13

What would you want to trigger that in the context of Connect Link?

14

First: Thanks for getting rid of the button that was not functional for our users! That should eliminate some confusion for the time being.

If you do implement the cancel_redirect_uri , then the close button would be the appropriate trigger

15

Got it. To be totally transparent I don’t realistically see us prioritizing that in the near future. Feel free to create a feature request here if you’d like to track it though: Sign in to GitHub · GitHub

16

Appreciate the transparency! I’ll file a feature request.

Thank you for prioritizing a fix, it will help with confusion on our end!

17

thanks