Typically, as we submit a new fax and get a jobID, the endpoint that serves JobDeliveryStatus is ready to go immediately. We check the first status after 67 seconds to catch the initial errors like 2006, 6500, 5103, 9001, etc., and then we check the status progressively in respect to the fax size. It works fine, but there are some rare cases when the 67 second status check does not return any status. We consider this an abnormality and initiate a resend from our side. Interestingly, all the resents failed with the same pattern: no job status (xsi-1823050305, xsi-1497425536, xsi-1823052613, xsi-1823052856). Despite this, OT does deliver the jobs successfully after they fail to report status at 67 seconds. So, what is your internal logic for when job status becomes available? Why is it available instantly in most cases, but in some rare instances, the status availability has a delay? We can certainly fix this on our side by allowing the job status absence to not be a terminal event. We can queue the failed status jobs, or we could extend those 67 seconds to a few minutes, but it would be helpful to know what happened on the OT side in terms of status availability.
