-
Type:
Feature
-
Resolution: Won't Do
-
Priority:
Standard
-
None
-
Affects Version/s: 2.1.13
-
Component/s: Data Transfer
-
None
-
5
Acceptance Criteria:
When request is found to be "Unknown" after a bestman restart, create a new request for the user.
Send an email to describe what happened (noting request failed, and a new one has been created)
Add toggle for this behavior.
Problem:
When bestman is restarted it loses its pointers to all the previous requests made by the gateway.
And when the gateway asks for an update for a particular request from bestman, bestman replies with a 'request unknown' error response.
With the new code we should hopefully be able to determine that the error is caused by bestman being restarted and then we could automatically resubmit our user's request for them.
Right now we just fail the user's request and they will have to resubmit that request themselves. This current behavior has caused a lot of confusion for folks and causes a reasonable number of help desk requests.
When request is found to be "Unknown" after a bestman restart, create a new request for the user.
Send an email to describe what happened (noting request failed, and a new one has been created)
Add toggle for this behavior.
Problem:
When bestman is restarted it loses its pointers to all the previous requests made by the gateway.
And when the gateway asks for an update for a particular request from bestman, bestman replies with a 'request unknown' error response.
With the new code we should hopefully be able to determine that the error is caused by bestman being restarted and then we could automatically resubmit our user's request for them.
Right now we just fail the user's request and they will have to resubmit that request themselves. This current behavior has caused a lot of confusion for folks and causes a reasonable number of help desk requests.