function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion

Outbound message hits webservice continously

have a webservice written in .net which gets the request from the outbound message and sends the response. But salesforce keeps hitting my application and it still waits in outbound queue. How do I stop salesforce to hit the application once the response is received? Following is my code sample

notificationsResponse INotificationBinding.Pur(PTrans.notifications PurP)
        string id,session = null;
        PTrans.notifications test = PurP;
        session = test.SessionId;
        string url = test.EnterpriseUrl;
        PTrans.Transaction__cNotification[] request = PurP.Notification;
        PTrans.notificationsResponse response = new notificationsResponse();
        response.Ack = true;
        return response;
When I tested with soapui, I get the following response,

<soap:Envelope xmlns:soap="" xmlns:xsi="" xmlns:xsd="">
      <notificationsResponse xmlns="">
The outbound message is fired only once. It will retry if the previous call fails.
Is it the same outbound message you see in the queue.

Satish Kumar

For every record is created or edited i have outbound message in the queue and my webservice sends back the response and update a field in salesforce. After updation it keeps hitting the application
Your callback trigger another message, you've created a notification loop. Checkout the triggers outbound messages profile option, if you disable this on the profile of the user making the update callback, this'll stop the loop.
@Superfell Do you ask me to disable the send outbound message option for the user? 
At present, I am testing with the System admin profile. 
Hi Sweetz,

Could you please suggest how you got the outbound message response and update a field in salesforce.

Its urgent please, can you please provide a solution.

Thanks in advance.
Mike Foote 1Mike Foote 1
This made me LOL :)
Rajat Sharma 84Rajat Sharma 84


you need to make sure your integration user who is sending update to SF don't have "Send outbound Message" permission. This is case of the infinite loop.