You are here:
Considerations for Outbound Messages
Review the considerations for using outbound message actions before implementing them in your workflows.
Required Editions
| Available in: Lightning Experience and Salesforce Classic |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
When creating outbound messages for workflow rules or approval processes, consider the following:
- A single SOAP message can include up to 100 notifications. Each notification contains an ID that uniquely identifies a record, and a reference to the data in the record. If the information in the record changes after the notification is sent, but before the notification is delivered, only the updated information is delivered. If the record is deleted before the notification is delivered, the notification contains no data.
- To preserve message reliability, messages are queued until they’re sent.
- If the endpoint is unavailable, messages stay in the queue until sent successfully or until they’re 24 hours old. After 24 hours, messages are dropped from the queue.
- The timeout for an outbound message is 60 seconds. The system tries to deliver an outbound message during the timeout duration.
- If a message can’t be delivered, the interval between retries increases exponentially, up to a maximum of 2 hours between retries.
- Messages are retried independent of their order in the queue, which can result in messages being delivered out of order.
- A message can be delayed by other, long-running messages in the queue. The queue can also contain messages that originate from other Salesforce orgs that are hosted on the same Salesforce instance. The system attempts to optimize the execution of messages that historically have fast run times so that they aren’t delayed by slow-running messages. To get the best performance, make sure that the message endpoint runs efficiently. For slow-running messages, consider using asynchronous processes, such as platform events or Apex future methods.
- You can’t build an audit trail by using outbound messages. While each message is delivered at least one time, it can be delivered more than one time. Also, if delivery can’t be done within 24 hours, the message doesn’t get delivered at all. Finally, the source object can change after a notification is sent but before it’s delivered, so the endpoint only receives the latest data, not any intermediate changes.
Did this article solve your issue?
Let us know so we can improve!
