Hello Celigo Team,
It seems there was an update that is causing this error to be thrown when there is an apparent invalid connection configuration:
The field connection.http.concurrencyLevel should be set to 1 when the field connection.http.rateLimit.limit is populated.
Not a big deal, should be easy to resolve, but the problem is that you can't save the corrective changes to the connection because the validation check detects the error still (i.e., it's looking at the saved state and now the just edited data).
The workaround is to remove the rate limiting configuration, set concurrency and Save & Authorized. Then edit again and restore the rate limiting settings and Save & Authorize again.
Not a huge deal, but could be improved.
Please sign in to leave a comment.