Apex Code Development You need to sign in to do that
Don't have an account?
zdooder Why are my failed outbound messages not being retried?
We are using outbound messages to synchronize updates to Salesforce data with an external database. I believe that this was working at one time, but I recently discovered that all failing messages are not being retried, and I'm trying to track this down and fix it. Specifically, I've configured my PHP outbound message processor to intentionally fail ALL messages just for testing. I have confirmed that Salesforce's Outbound Message web request is receiving the following SOAP reply:
I've seen some sample XML responses posted that are slightly different than this but (1) this is what the PHP SoapServer class is generating as defined by the WSDL, and I'd prefer to use that rather than generating a custom response by hand, and (2) I think the namespace definitions, while different, are equivalent. I also feel like any HTTP status code of 500 should be considered an error by Salesforce, but I included a full SOAP response anyway just in case that made any difference. I've also tried using 400 HTTP status codes with the same result.
I've confirmed that I've got current WSDL for the outbound message. I can see the outbound message in the queue when it gets sent, but it appears to just "go away" after that.
I'm kind of at my wit's end here because I can't understand why that response is being taken as a successful result. Any suggestions?
Thanks,
Troy
HTTP/1.1 500 forcing failure for testing Date: Tue, 12 May 2020 22:00:20 GMT Server: Apache/2.4.18 (Ubuntu) Content-Length: 300 Connection: close Content-Type: text/xml; charset=utf-8 <?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://soap.sforce.com/2005/09/outbound"><SOAP-ENV:Body><ns1:notificationsResponse><ns1:Ack>false</ns1:Ack></ns1:notificationsResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
I've seen some sample XML responses posted that are slightly different than this but (1) this is what the PHP SoapServer class is generating as defined by the WSDL, and I'd prefer to use that rather than generating a custom response by hand, and (2) I think the namespace definitions, while different, are equivalent. I also feel like any HTTP status code of 500 should be considered an error by Salesforce, but I included a full SOAP response anyway just in case that made any difference. I've also tried using 400 HTTP status codes with the same result.
I've confirmed that I've got current WSDL for the outbound message. I can see the outbound message in the queue when it gets sent, but it appears to just "go away" after that.
I'm kind of at my wit's end here because I can't understand why that response is being taken as a successful result. Any suggestions?
Thanks,
Troy
Incase you/someone is still looking for an answer-
As per, https://help.salesforce.com/articleView?id=workflow_tracking_outbound_message_delivery_status.htm&type=5
"Failed outbound messages failed to be delivered and are no longer being retried. Messages are listed here only if you configure the message when you create it by selecting Add failures to failed outbound message related list. If you do not see this related list, it has not been enabled for your organization."
Please ensure the "Add failures to failed outbound message related list" is enabled on your org.
Hope this helps. Please mark this answer as best so that others facing the same issue will find this information useful. Thank you