Offline transaction processing doesn't alert user when failing

[Terran McCanna]

When processing of an uploaded offline transaction file stops before completion, the screen still says "Yes" under the Processing column for a lengthy amount of time and does not give the user access to the errors that have been generated up to that point.

The user can tell that the processing has failed if the number of transactions processed does not change after refreshing the screen. (See attached screenshot which shows a process that failed to complete after a day, but still shows "Yes" under the processing column.)

For the wish list:

Ideally, if processing did not complete after a certain length of time, a "did not complete" type of message would appear in the status column, and the errors that had been generated up to that point would be made available in the event log portion of the screen.

[Andrea Neiman (aneiman)]

I'm wondering if this is still an issue in the web client? I suspect it would fail differently, but I don't think a specific timeout mechanism is part of the new Offline code. Would be worthy of some testing to see how this differs, or reports from current users of Offline about whether/how this is happening.

[Terran McCanna (tmccanna)]

I suspect it's no longer a problem in the web client, but I haven't been able to come up with a way to get it to fail to test it.

[Terran McCanna (tmccanna)]

I'm going to mark this one Won't Fix since it was specifically related to the XUL client.