AB_Job_StatusNew |
Job is new and not yet enqueued. |
AB_Job_StatusUpdated |
job has been updated by the backend and is still not yet enqueued. |
AB_Job_StatusEnqueued |
Job has been enqueued, i.e. it has not yet been sent, but will be sent at the next AB_BANKING_ExecuteQueue(). These jobs are stored in the "todo" directory. |
AB_Job_StatusSent |
Job has been sent, but there is not yet any response. |
AB_Job_StatusPending |
Job has been sent, and an answer has been received, so the Job has been successfully sent to the bank. However, the answer to this job said that the job is still pending at the bank server. This status is most likely used with transfer orders which are accepted by the bank server but checked (and possibly rejected) later. These jobs are stored in the "pending" directory. |
AB_Job_StatusFinished |
Job has been sent, a response has been received, and everything has been sucessfully executed. These jobs are stored in the "finished" directory. |
AB_Job_StatusError |
There was an error in jobs' execution. FIXME: Does this mean the job is enqueued, sent, pending, or none of these? How can the App be sure that the job isn't accidentally enqueued again? |
AB_Job_StatusDeferred |
Jobs was enqueued but then deferred i.e. removed from the queue, and nothing will happen anymore with this job. |
AB_Job_StatusUnknown |
Unknown status |