We deployed a fix for a server-side issue that caused this behavior on Monday evening around 7 PM PDT (2018-07-03 02:00:00 UTC). We apologize for the inconvenience this has caused.
Please do let us know if you see the continuous prompting for consent behavior going forward.
Thanks and regards
I have similar problem with SQL Server connection.
Anytime users open the app - it shows a screen with request to Allow conenction.
App and the connectection are shared correctly.
Do you know what could be the reason?
We also seem to be encountering this same issue for the SQL connection. I tried with both users on the Gateway and users not on the Gateway with the same result.
Session ID: aabb42b8-2ee0-480c-9c52-1e54f1645ea4
Dear Power Users Community,
Thank you so much for the reports you have submitted regarding this issue. We have identified a defect that is related to the one previously fixed that is affecting a subset of shared connection cases (typically apps that use SQL connections).
We are working on a fix now - we should be able to get this cleared up before the weekend is out.
We are terribly sorry for the inconvenience this has caused your users!
We have deployed a fix globally and our telemetry indicates the issue has been resolved. Could you please confirm that the app behavior has returned to normal?
Thank you again for reporting the issue, and we are sorry for the inconvenience.
We are using an API custom connector and still seeing the issue with one of our apps. It is asking for permission for the connection everytime.
Hi there PSahu,
Sorry for the delayed response. Your issue is different than the issue that was already fixed as discussed in this thread. The error we see in the logs is this one:
'The request failed with error: 'Input parameters are invalid. See details for more information. Details:errorCode: KeywordLimit. Message: Only 40 keywords allowed per entry..'.
This happens when you have the same connection used in more than around 35 canvas apps. Unfortunately the client doesn't currently have good error handling for this case - what it means is that the system attempted to tag the connection with the application it is used within, and we hit the limit of tags (the tags are per user and used to associate the connection with the app for that user).
The workaround here is to partition connection usage across your apps. That is you can create two or more connections to the connector and limit the usage of each connection to something like 25-35 apps (the exact limit depends on other tags that could be applied depending on various scenario factors, so 25 should be a safe target).
We most commonly see this issue crop up with shared connections like the SQL Server connector.
We are working on both a short term and long term improvement here:
1. Short term - provide an appropriate user experience when you are approaching the limit
2. Long term - substantially increase the limit
Sorry for the inconvenience this has caused your app users!
Thanks and regards
We're excited to announce our first cross-community 'Can You Solve These?' challenge!
Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.
We are excited for the next Super User season.
FIll out a quick form to claim your community user group member badge today!
Features releasing from October 2020 through March 2021