This topic was automatically generated from Slack. You can find the original thread here.
I’m trying to connect a ServiceNow instance according to the instructions in the docs, and I get to the point where I approve the authorization, but then eventually get a 504 error, that lands on a Pipedream URL. Is there a potential issue here? I’ve confirmed the settings within ServiceNow and I’m sure they’re correct, but I don’t know if this timeout is saying that Pipedream didn’t respond to ServiceNow, or that my ServiceNow instance didn’t respond to Pipedream.
So, very weirdly - when I went back in just now to add a new connected account to get the full URL, there was an active ServiceNow connection, and I just ran a test and it seemed to work….so! That’s a bit of a mystery. Looking at my browser history though, this was the URL:
So if that helps troubleshoot at all, great - otherwise I’ll keep going. I am currently setting up a connection to our dev instance, and OAuth registries get reset when moving between instances, so I’ll have to do this again when we go to test and prod anyway…so if there’s anything to learn, let me know!
It may have been an intermittent issue with just the OAuth handler on our end, based on that URL. I’ll forward this along and hopefully we have an error trace we can diganose from
