Find your content:

Search form

You are here

Workflow - Outbound Message lost?


If someone could oblige:

When you spawn an Outbound Message (my workflow literally says "on every edit", if the last name is not blank...), and it is supposed to hit a URL and send 3 fields (including a Contact ID let's say)...

Can those HTTP calls be BUFFERED on Salesforces end?

And, would anyone know a reason why these calls frequently never (appear) to come through? Our WebDev has a simple PHP page that accepts the Contact ID and runs a process on the web server... but we're noticing 1 out of 7 (frequency varies) of the hits actually register on the web server (which is at NatNet).

Any insight would be appreciated.

If it matters: (that's the URL being called)

Attribution to: AMM

Possible Suggestion/Solution #1

Outbound messaging implements an at least once delivery protocol on top of SOAP, the server will try to send the message until it has been actively acknowledged by the receiver (by returning true in the soap response). The server will back-off the retry interval after each failure.

One thing to be aware of is that a single SOAP message can contain data for upto 100 records, make sure you're processing the entire payload, and not assuming that they'll only be a single record in it.

Attribution to: superfell

Possible Suggestion/Solution #2

You can monitor the outbound messages which have queued up for failed delivery at Setup > Monitoring > Outbound Messages

Attribution to: techtrekker

Possible Suggestion/Solution #3

Three points

  1. Yes, the can be buffered or rather collated, so that if you did a mass update or insert, you'll get up to 100 notifications in a single soap call. Make sure you handle that in your client. (That said, single record updates should result almost immediately in an outbound message being sent.)

  2. Is your workflow rule correct, there isn't a logical flaw in it meaning it doesn't trigger?

  3. Have you check the outbound message queue to see if you have undelivered messages?

I'm in the process of testing my own outbound messaging stuff at the moment and I haven't seen Outbound messages being 'lost' yet. It's always been 2,3 or my client eating the SF message and not informing it of a failure in processing.

Attribution to: Steven Herod
This content is remixed from stackoverflow or stackexchange. Please visit

My Block Status

My Block Content