Try increasing the timeout window in the connectorAttributes of the source. These two attributes have worked for me in the past, but not for this connector specifically:
“healthCheckTimeout”
“timeoutInSeconds”
Also, try enabling connector logging and check the ccg logs for any extra clues. The UI error typically doesn’t give the full picture.
Thank you for your recommendation. After I added the healthCheckTimeout value, the error changed to a different one. However, I’m not sure how to configure and view the logs for this application.
But in this case, I haven’t set up a VA for the application, as shown in the screenshot on the topic post. Could you please advise me on how to properly configure logging and where I should be looking to access these logs?
Ah I see, this is definitely a SaaS based connector and doesn’t go through the VA. You won’t see any logs in the VA’s for this connector.
Only other thing to check would be to go over the configuration guide again and ensure you have done the setup correctly and assigned all the required permissions.
If all else fails after that, I would open a support ticket to see if SailPoint can see any logs on their end to help assist you.