Jarett:
If processing time is the issue, you should see a failed OB Message attempt with a "Timeout" or similar message in your OB Message queue between the first and second request.

Whether or not this is really the issue, you could resolve it by creating your own processing queue.

What I mean is: when your site receives the Message from SalesForce, store the (serialized and/or encoded) data locally and send the ACK back to SalesForce right away. Then, again locally, set up a periodic process (cron or similar) to do the processing on your own time, while SF isn't waiting for a response.

Separating your processing logic from your soap transaction logic will also help make your code more reusable.

if anyone gets a chance to throw their $0.02 in, i just posted a new outbound-message-related thread with a new issue:

http://www.mikesimonds.com/outbound-...2.html#post780

thanks in advance,
/a

It never has sent a timeout message that you described. Occasionally it will send a blank OB back, but nothing with a timeout value or anything else. It's just a typical message, except it has no notification elements. When I took a look at the execution time, we are posting a response 95% of the time within a second or two of receiving the message, so I'm not sure where the issue is with getting multiple outbound messages is coming from. We've already programmed around the issue, but it would be nice to not have to had dealt with it.

Hmm, that's strange indeed. Do you have some complicated workflows or triggers set up that might be firing the same message more than once for a single action? The only other thing I could think of is that it's a network/connectivity issue...

The process is this:

Obtain the SoapMessage
Parse it
Save the Data to the DB
Return the response

The whole process may take 3 seconds from the time the SoapMessage gets to us to the response being posted.

Not sure what it is. We've got a lot of data manipulation AFTER the response, but other than converting a date to a different format with about 5 lines of code, nothing before.

There is only one place co respond in the code, so it's not like it is wrapped in a loop or something.

Either way, we've programmed around the issue, so it's not like it is a problem, just a nuisance.

I'm having a similar issue in regards to timeouts, I have an outbound message tied to an approval process. I get timeout issues when that approval process is executed in bulk, eg. approve 100 records all at the same time. it tries to send 100 requests at the same time which in turn causes timeouts, most likely because my server can't handle that many requests at a single time.

Until I can upgrade my servers or queue up the requests on my end and handle the processing after, I was wondering if anyone knows if it's possible to slow down outbound message queue in SF, essentially forcing SF to send the OM's separately with several seconds apart???

I don't think there's any way to throttle the OBM queue. However, I've had success with chunking bulk operations into 10 or 20 updates at a time.

Anyone,

ok Needs some help for a multiple notification SOAP post, page 2 of this thread is great except I need the id for each notification as well. How can I get this?

SAMPLE

Code:

   <?xml version="1.0" encoding="UTF-8"?>
  <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soapenv:Body>
    <notifications xmlns="http://soap/outbound">
     <OrganizationId>ABC...</OrganizationId>
     <ActionId>123...</ActionId>
     <SessionId xsi:nil="true"/>
     <EnterpriseUrl>https://Url>
     <PartnerUrl>https://Url>
     <Notification>
      <Id>mmm1</Id> // WOULD LIKE THIS ID
      <sObject xsi:type="sf:Case" xmlns:sf="urn:sobject.enterprise.soap.sforce.com">
       <sf:Id>333a</sf:Id>
        </sObject>
     </Notification>
   <Notification>  
    <Id>mmm2</Id> // WOULD LIKE THIS ID
      <sObject xsi:type="sf:Case" xmlns:sf="urn:sobject.enterprise.soap.sforce.com">
       <sf:Id>333b</sf:Id>
        </sObject>
     </Notification>
    </notifications>
   </soapenv:Body>
  </soapenv:Envelope>

So are you saying that you are not seeing all the ID's when your outbound message is processed by the function?

Sorry i am a little confused with your posting

What im trying to say is the ID tag after the notification tag and before the sObject tag(s) is not being captured in your code examples and I dont see how I can get this value. The value is different for each notification tag so it could have multiple values if there is more than one notification tag. In my code example above I have two notifications tags so there would be two ID's I would need to get. I know the value needs to be in an array but I'm new to SOAP and Salesforce so it's a little unclear on how I could do this.