T
Torben Frandsen
In the legacy API I'm trying to find a way to notify the user if the job
failed permanently or if it's queued for retry. Obviously this isn't easily
accomplished since both DeviceStatus and QueueStatus are set to Unknown in
both cases.
Has anyone tried to create a workaround for this limitation?
One thing I tried was to create a field called RetriesLeft and initially set
it to Server.Retries. Then I would decrement it whenever the two statuses
changed to Unknown. Bad idea. Even when the job is queued for retry, the
statuses cycle between Available, Pending, InProgress and Unknown.
Any ideas for a solution are welcomed. Unfortunately we can't switch to the
new API at this point.
Torben
failed permanently or if it's queued for retry. Obviously this isn't easily
accomplished since both DeviceStatus and QueueStatus are set to Unknown in
both cases.
Has anyone tried to create a workaround for this limitation?
One thing I tried was to create a field called RetriesLeft and initially set
it to Server.Retries. Then I would decrement it whenever the two statuses
changed to Unknown. Bad idea. Even when the job is queued for retry, the
statuses cycle between Available, Pending, InProgress and Unknown.
Any ideas for a solution are welcomed. Unfortunately we can't switch to the
new API at this point.
Torben