Request In Processing queue

We have recently run into some trouble due to the fact that once a request is opened by a staff member, it remains in the Request In Processing queue indefinitely if no action is taken with the request, even after the staff member closes down her machine for the evening. 

Here is an example of how this causes problems: My colleague opened a new request on a Monday morning. She was called away from her computer and the request remained in the Request In Processing queue. She must have forgotten about it at that point. On Thursday afternoon of that week, I noticed that we had a patron coming on Friday and I looked up his name in Aeon. I saw that he had a request in Request In Processing. By that time, it was too late to order his material from off-site storage in time for his arrival on Friday morning. Since the patron was coming from five hours away, we had to do all kind of strings-pulling and acrobatics to get the boxes to him in time, all because one request window was left open and forgotten.

Is there any way that requests in the Request In Processing queue could automatically revert to whichever queue they had been in previously, after one or two hours? This way, if someone opens a request and forgets about it, it doesn't languish in the Request In Processing queue indefinitely, causing problems such as the one described above.

0

Comments

3 comments
  • Hi Isabel,

    This does not sound like expected behavior. When the request is closed (even as the computer is shut down), the request should move back to it's original status from Request In Processing, as you'd expect. We have heard a similar issue from another Aeon site where requests get stuck in Request in Processing even after staff have closed the requests. Thus far, it isn't something we've been able to reproduce. But if you see this happen again, could you send client logs from the related computers to support@atlas-sys.com so we can see if anything is reflected there?

    In the meantime, I'll take this to the Aeon Product Team to discuss whether there is a better way to handle this, including what you've proposed. It may result in a UserVoice enhancement, which I'll share a link to, if relevant.

    Best,
    Katie

    0
    Comment actions Permalink
  • Hi Isabel

    Here's a couple of best practices to help you while Katie works with the product team.

    1. Encourage folks to log out of the Aeon Client at the end of the day. This should close the Request In Process requests. If it doesn't, definitely let us know at support@atlas-sys.com. If a computer is set to 'sleep' or 'hibernate' mode at the end of the day, the Client may leave the requests open.
    2. Have someone periodically open the Request in Process queue and check the Transaction Date field for requests that may have been forgotten.

    0
    Comment actions Permalink
  • Hi Katie and Heather,

    Thank you for your responses. I have passed along your messages to all of the staff here. We'll be on the lookout for other examples of this error occurring.

    Best,

    Isabel

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post