logging out of the staff client while offline transactions are being processed will cause NO_SESSION exceptions for the remaining transactions

[Jason Etheridge]

The problem here is that the Admin -> Manage Offline Transactions interface leads one to believe that it can run independently of the current login session, but it in fact makes use of the same authtoken, so if you log out and destroy that token, any remaining offline transactions being processed will fail.

-- Jason

[Erica Rohlfs (erohlfs)]

Confirmed in Evergreen version 2.9.0

[Andrea Neiman (aneiman)]

This needs to be tested to see if it's still a problem in the web staff client. Obviously the interface is different, but I suspect that logging out of webby mid-processing will cause a similar failure.