obfscUser-lockOut-qryCancelled-2.png
screenshot-1.png
[CORE-281] Query continues to run after user receives lockout message Created: 08/Dec/17 Updated: 01/Jun/22 Resolved: 01/Jun/22 |
|
| Status: | Closed |
| Project: | i2b2 Core Software |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.7.13, TBD |
| Type: | Bug | Priority: | Minor |
| Reporter: | Janice Donahoe | Assignee: | Reeta Metta |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
obfscUser-lockOut-qryCancelled-2.png
screenshot-1.png
|
| Participant/s: |
| Description |
|
When an obfuscated exceeds the allowed number of times they can repeat a query they will be "locked out" from running another query. When they receive the message telling them they have been locked out, the system should cancel the query they are trying to run. However, when they click on OK the Web Client continues to run the query.
EXAMPLE: lockout count = 7 obfuscated user runs same query 7 times and gets results returned each time. The next time (8th time) the obfuscated user runs the query, the status of Cancelled will display in Show Query Status. However, when you look in the qt_query_master table the query doesn't have a DELETE_DATE or DELETE_FLAG which indicates the query was not cancelled as indicated in the Web Client. |
| Comments |
| Comment by Jeffrey Klann [ 04/May/22 ] |
|
Problem might have been fixed with |
| Comment by Reeta Metta [ 01/Jun/22 ] |
| When user runs the query after lock out(7th attempt), query will be cancelled with ERROR msg and previous query shows ERROR status. see screenshot |