Has anyone started hitting more 401 login errors r...
# suiteql
a
Has anyone started hitting more 401 login errors recently with SuiteQL? I'm noticing from about ~2 weeks ago that previous processes for syncing large accounts have started hitting an elevated level of 401 login errors, which I usually attribute with timeout issues from Netsuite's side...
e
Where does the call come from?
a
Our backend of our product- unfortunately I am not a backend engineer so I don't know the specifics, but if you have any hunch on what could be causing this would love to hear! I was wondering if there was a way we were generating the token, or a header we aren't passing in that signals to keep the connection alive longer that we were missing??
e
Hard to tell. We have a third party integration that touches 2 different endpoints: a middleware and NetSuite (its a sync job). When we have timeouts they always have been in the middleware layer, not in NetSuite.
a
We directly hit Netsuite!
And usually retrying the request will remedy the immediate 401, but then a new one will hit a 401 like a couple minutes later
b
TBA and the Login Audit Trail is the usual place to start
if its a intermittent signature related error, then whoever implemented your authorization related code likely is not encoding the values in the authorization header
a
They are for a customer account, so we don't have immediate access to login audit trail unfortunately 😞 it's super weird bc it will run requests fine that are less than a minute response times, but requests longer than a minute it will immediately return a 401
But in postman, we can get those requests to come bacck
b
you arent going to get very far without the logs
so either get the logs or reproduce the problem in an account you control