Time out with JobDeliveryStatus

I am trying to get the jobDeliveryStatus for this job is there any way we can add time to this?

jobIdType.MRN = #"11791284"#

jobIdType.XDN = #"xsi"

#Error Message:

System.TimeoutException: The request channel timed out
while waiting for a reply after 00:00:59.9531979. Increase the timeout value
passed to the call to Request or increase the SendTimeout value on the Binding.
The time allotted to this operation may have been a portion of a longer timeout.
---> System.TimeoutException: The HTTP request to
'https://messaging.easylink.com/soap/sync' has exceeded the allotted timeout of
00:01:00. The time allotted to this operation may have been a portion of a
longer timeout. ---> System.Net.WebException: The operation has timed
out

at
System.Net.HttpWebRequest.GetResponse()

at
System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan
timeout)

Find more posts tagged with

Comments

skamens

The timeout value is completely controlled on the client side (i.e. on your system). The API does not impose this timeout.

In this case, the job you are querying for only has 1 item - I wouldn't expect a JobDeliveryStatus call to take anywhere near a minute.

I searched our logs for this job number, and I do see a request being successfully processed at 12:10 PM (Eastern Time). The response was returned by our system within a second.

Did you get that response successfully?

clint.whitehead

Hello,

That helps a little.. ill read though the docs and see what I can come up with.

Thanks

clint.whitehead

Oh and to answer your question I ran this through twice.. the first is when I got than error and didnt recieve a successful response.. the second time I was able to get the sucessful response

clint.whitehead

Good Afternoon,

I think I understand what you mean now.. are you saying that there isnt a feild in the JobDeliveryStatus Request for me to pass in a number to have more time for the timeout?

Clint

skamens

That's correct. The timeout is handled by the software you're using to send the request from your side; generally there is an option you can use to set that value, but it's not related to the API or its schema.

If all your jobs are small like the one you're testing with, the default (which seems to be 1 minute) should be plenty. You just need to have a little error handling in your application to deal with the occasional glitch.