This occurs because the API is taking more than one minute to respond, primarily due to the extensive backend operations required during user creation. As per the documentation, the command timeout is three minutes, and our API is not taking more than two minutes to respond.
I also attempted using response.keepAlive(), but as you know, it still requires a response.send() afterward. If we return any response, SailPoint ISC will process it and attempt to run a Create Account operation on that response. Sending another response later would trigger the Create Account operation again, which is incorrect.
Could anyone please advise if there is any way to keep the connection alive for the Create User operation ?
I set the provisioningTimeoutvalue to 180 and it is working able to create accounts. But I can only set it for a specific source right now meaning everyone who installs my connector will have to set it. Can anyone suggest how to set it for the entire connector?
I’ve had this same issue happen on a connector that I was creating. I had keepAlive calls seemingly everywhere and it didn’t seem to make a difference.
This topic was marked as solved but I’m not sure it was
There was another topic that I looked at where someone had their connector logs listed and the timeout occurred much shorter than the spec says it should.
Can you post your connector logs with timestamps? The log should have a keep alive count and the timeout errors will show as well. We should be able to see when they’re occurring