nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Job State

nithiiy

Hi,

I am trying to find out when to stop looking for updates from a Job. We have setup all inbound faxes to be forwarded to an ftp address and two email addresses. Individual item state says 'error', 'sent' and 'sent' respectively (ftp failed). Job State says 'Delivered, Posted'.

By looking at this discussion https://apiforums.easylink.com/content/job-delivery-status it looks like a Job State of 'Complete' is the end of the job. So, in my case do i have to keep looking for updates till the Job State changes to 'Complete'?

Find more posts tagged with

Comments

nithiiy

hi, could you please check this?

thuneke

You should look at the State for the individual items. A State of Sent can be considered done. For a State of Error, you need to look at the gamma code provided to see if it is a soft error, such as busy and will be retried, or if it is a hard error, such as bad number or ftp failed. Those can be considered done.

The Job State will not go to Completed until all items are done.

skamens

The above comment is true, but if the Job State shows Posted or Delivered, the main deliveries have been done.

It will go to Completed after reporting is finished, and possibly after a delay due to keeping the job available for a while for subsequent reporting.

nithiiy

Hi,

I have an inbound fax where the entry time is '2012-05-25 23:35:45.0000000' and we have set it to forward to an ftp address, and two email addresses. The individual item states for three items are 'error', 'sent' and 'sent' and the job state is 'Posted, Delivered'. It has been more than 3 days and still the job state has not changed to 'Complete'. Any reason why? how long does it take for the job state to change to 'Complete' from 'Posted, Delivered'?

thanks.

skamens

Please provide the job ID so we can investigate.

nithiiy

test2

1841547

skamens

The reason this job is held up is because of a problem in the reporting of the error.

When the system fails to deliver an inbound fax, it attempts to deliver a failure notice to the administrator of the account to inform them of the failure.

However, the configuration that allows the inbound fax to go to multiple destinations actually trips up the logic that determines where to send those failure notices, and that causes the job to be held up.

Normally in production, these errors get handled quickly, but the test system isn't quite as tightly monitored, and that kept your job from completing.

I have pushed the job to complete so you should see the Complete state now.

nithiiy

thanks. so,

1. delivery failure notice is a default functionality of the system or can we modify the settings?

2. will this problem continue to exist in the test system? if yest, then how do I do complete testing?

skamens

The delivery failure notice is a function of the system; there might be some ways to turn it off via configuration, but off-hand I'm not sure how to do that.

I did try a configuration change to see if that will work better for you. Can you try submitting another test to see if the job completes in a more timely manner? If not, I have a couple of other ideas that might be a bit more complicated to try, but we'll go there if we need to.

nithiiy

test2 - 1867977. job state still not changed to 'Complete'

entry time = 2012-05-29 19:49:15.0000000

posted time = 2012-05-29 19:49:00.0000000

nithiiy

hi, were you able to figure it out?

thanks

skamens

I have figured out why this is happening - it is actually due to a software bug in our system.

There is one profile setting I would like to try to see if it helps with this. It may slightly change the way the emails look when they are sent to you.

Would it be OK if I made that change and sent another fax to your number?

nithiiy

ok no problem.

nithiiy

hi, any updates?

thanks.

skamens

Sorry for the delay.

I made the small configuration change and ran a test (JobId test2/1866542). This one did not get delayed and went straight to complete.

You might also have received an error report due to the failed delivery.

Let me know how this works for you.

nithiiy

Thanks. It now goes to Completed state (Hope, this won't be an issue in production). However, i did not receive any error report for failed delivery. do you know to whom the error report are addressed to?

skamens

The issue will not occur in production as long as your account has the setting I did on your test account. Once you know your production credentials, let us know and we'll make sure the settings are correct.

As for why you're not getting the error report, I believe that is because your account is at the top level of the administrative hierarchy in fax2mail, and the system wants to send the report your adminstrator (who doesn't exist).

If you're already tracking this via the API, I don't think the error report matters much - correct?