Is SuperTokens having an outage?! My Lambdas are suddenly timing out completely!
a
Is SuperTokens having an outage?! My Lambdas are suddenly timing out completely!
r
Hey!
Hey.
a
Hey there
r
There was no outage whatsoever
Not were there any errors
Nor*
Did you figure out why the lambdas were timing out?
a
nope
I ended up switching cores
r
Huh.. so you created a new account on our site?
a
nope, one of my devs had signed up last month for a free account
r
I see.
a
we had been doing testing against that account while we were under development
that core suddenly stopped working
so I moved our primary integration environment over to the new dev core
r
Do you mind messaging me the account email ID for the one that stopped working?
a
should have been roy@gosweft.com
r
Right ok. I’ll check it out and get back. But there were no errors from our side at all.
So this is strange
Do you also mind sharing the error stack trace?
a
not stack trace
lambda just ran for 30s until timeout
r
Hmmm. That could hint at another issue
Are there any logs at all from that lambda?
a
nope
died at getSession
r
So getSession doesn’t query the core 99% of the time anyway
But since this is a serverless func, on start it should have queried the core to get the public keys
a
that makes sense
r
Can you enable backend debug logs, switch back to the previous core credentials and see if that works?
a
That was the URL we were hitting
r
Gotcha. So that seems to be working fine
a
I honestly don't have time to switch back to the previous core tonight
r
Fair enough
a
I'm very far behind on work
r
No worries
a
How do I turn on backend debug logs?
I'll have one of my devs turn them on in their sandbox
r
You need to pass an env var DEBUG=com.supertokens to the lambda
a
oh, right, I saw that once
thanks
I'll put that in next time
r
Cool thanks
Also for future, you can subscribe to https://supertokens.instatus.com/
If you think the SaaS is not working, then see if there are any issues in there.
a
thanks
r
If there are no issues there, then something else might be wrong. And if that says that it has an issue, then it means at least one of our users is facing an issue - it may or may not be you.
And another way to know is to visit the core’s connection uri on the browser. If you visit the /hello path, and it gives back Hello, it’s working
a
oh nice,, I had no idea that was a feature
Thanks for the tip
r
👍
a
ok, I'm experiencing the timeout on the new core
I'm going to try to turn on debugging now
r
Cool
a
no logs
r
That could either mean the env var has not been correctly set, or that the lambda function isn’t running at all
And this was not happening before right?
a
it just started today
the lambda function is running
I see it start and then stop due to timeout
r
Can you console log something right before and after calling supertokens.init?
a
yeah, I'm trying that next
debugging worked this time
r
Hmm
a
and I didn't time out.....
r
Hmmmmm
a
what in the hell
r
Well, keep the debugging on. Will be helpful next time the issue comes
a
it's logging a ton of "undefined" s
r
Can I see the output?
2 Views