Error Status Changes From Error to Complete

We recently went live with a client deployment in Australia. We are seeing hundreds of cases where the status code returned and logged is an error code, but later when the status is re-checked the status shows Complete. Is there any scenario where the service would return an error code, but retry delivery, and later update the status to Complete? For example, if only 2/4 pages got sent, the service returns an error status, and later the fax is sent in full and that Job ID status becomes Complete?

Find more posts tagged with

Comments

skamens

The short answer to your question is yes - there are situations where the status can change from Error to Complete.

Can you clarify whether you are talking about the job level status (available for JobList, for instance) or the item level status (available via JobDeliveryStatus or JobDetail)?

If you can provide some job number examples, we might be able to explain what you saw.

keithgagne

I am looking at DeliveryDetailType.State.code for the individual fax transmission status to the end recipient. Is it possible for the value to be returned as Error, Cancelled, Expired, or Held, and later become updated as Sent?

Example: {xsi}:{73676803}

skamens

Yes, it's possible for this to happen, although I don't see evidence of that for the example you provided above.

This kind of thing most often happens when a delivery fails temporarily (for instance, if it gets a busy signal trying to delivery a fax), and then succeeds on a retry.