Unexpected request status/Cannot have more than one request with the same position in the queue
Description
CSP Request Details
CSP Rejection Details
Potential Workaround
Attachments
relates to
Checklist
hideTestRail: Results
Activity
Micah Walter December 12, 2019 at 7:37 PM
I got this error again in the BugFest Q4 2019 instance. It occurred when duplicating a request in the queue. I haven't been able to replicate this since then.
Cate Boerema October 18, 2019 at 3:57 PM
Brilliant! Thank you !
Matt Reno October 18, 2019 at 2:55 PM
, yes, this was caused by request repositioning failing after the first request was closed - filled. This failure caused the loan to not be created.
Cate Boerema October 18, 2019 at 2:14 PM
Hi . We found another request in Chalmers production may have been Closed - Filled when it shouldn't have. Is there any way you can tell if it is caused by this issue?
The request is Closed - Filled, but when you click through to the requester's user record and then look at the loans for that user, there are no open or closed loans for this request.
Cate Boerema October 13, 2019 at 3:30 PM
Actually, this is interesting. The time I saw the above error, the request expiration date was saved and the request turned to "Closed - Unfilled" after just a few moments. When I tried this again, the error wasn't shown and the request expiration date was saved BUT the status isn't changing from Open - Not yet filled to Closed - Unfilled.
This seems like it might have overlap with the issue being worked on by and ()
Details
Details
Assignee
Matt RenoReporter
Micah WalterPriority
P3
This bug has been hard to replicate. I did record a [screencast of it](https://youtu.be/fETAUsDa_NM) (though it is not the most tidy presentation ever) – and I have a [longer recording](https://youtu.be/K_uogSqVtok) which includes 4 minutes of possibly irrelevant muddling around, but is where I created the initial requests.
NOTE: There are some repro steps to check and test in , as well
I am in the BugFest q3.2 environment, and logged in as mwalter.
As best as I can make out, these are the important things I did:
Steps:
Create two requests under item A.
Create four requests under item B (same instance).
Check in both items so that they are placed in transit.
It will be impossible now to move either request in position 1.
Move the request on item A in position 2 to item B.
This is where I got the error described above.
I have also seen this wording in a JSON modal format (see screenshots), but I have not been able to replicate that under controlled circumstances.