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
Woody ZantzingerWoody Zantzinger 

Web to Lead silent failure

Hi, having a problem with our Web to Lead system, which has previously been working fine for 6 months.

Our debug logs show successful web-to-lead submissions to Salesforce, but not all leads are actually importing. There is no clear pattern as to when/why a lead is not being imported. The default user is being monitored, and does not show any reports of failed leads, but does show succesful submissions. Submission is done through a WordPress add-on to the Gravity Forms plugin, but we have ruled out plugin errors, and our tests with Postman and with HTML forms generated by Salesforce itself show similar erratic behavior.

We do have a validation rule, but have turned it off and we are still experiencing the problem.

Our Wordpress logs show:

2014-05-09 5:31:05 - DEBUG --> This is the data sent to Salesforce (at https://www.salesforce.com/servlet/servlet.WebToLead?encoding=UTF-8:
Array
(
    [body] => Array
        (
            [email] => sample@sample.com
            [last_name] => John Smith
            [company] => Google
            [phone] => 5555555555
            [message] => Test
            [description] => Test
            [txt_medium__c] => (none)
            [txt_source__c] => (direct)
            [txt_campaign_name__c] => (direct)
            [txt_content__c] => -
            [txt_term__c] => -
            [txt_visitor_id__c] => 9999999
            [oid] => (Removed from Log, is the correct Salesforce ID)
            [debug] => 0
            [debug_email] => 0
            [retURL] => http://www.google.com
        )

    [headers] => Array
        (
            [user-agent] => Gravity Forms Salesforce Add-on plugin - WordPress/3.8.3;
        )

    [sslverify] => 
)
) 
2014-05-09 5:31:05 - DEBUG --> The `is-processed` header isn't set. This means there were no errors adding the entry. 
2014-05-09 5:31:05 - DEBUG --> Entry 1056 was added to Salesforce. Here's the available data:
Array
(
    [headers] => Array
        (
            [date] => Fri, 09 May 2014 09:31:05 GMT
            [cache-control] => private
            [content-type] => text/html;charset=UTF-8
            [connection] => close
        )

    [body] => 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE">
<meta http-equiv="Refresh" content="0; URL=http://www.google.com">
</head>
<script>if (this.SfdcApp && this.SfdcApp.projectOneNavigator) { SfdcApp.projectOneNavigator.handleRedirect('http://www.google.com'); }  else if (window.location.replace){ window.location.replace('http://www.google.com');} else {;window.location.href ='http://www.google.com';} </script></html>

    [response] => Array
        (
            [code] => 200
            [message] => OK
        )

    [cookies] => Array
        (
        )

    [filename] => 
)
The entry referenced in the logs above was not added, and Salesforce showed no errors or logs. The default user is being monitored, and shows logs if something is succesfully submitted.

Anyone have any thoughts?
Stony Grunow - BreadwinnerStony Grunow - Breadwinner
Hi Woody

We're getting the same issue with one of our clients. Salesforce is blaming everyone but themselves. Oddly, it stopped working on Monday, started working on Thursday for a few hours and then stopped working again. Setup audit logs show no change to Salesforce. No error messages are shown when the lead fails, and setting debug=1 shows the leads are being queued properly.

I'll pass this along to our clients, and hopefully Salesforce will get back to you. If you have a case number, please post it here. I'll ask my clients for their case number.

stony
Woody ZantzingerWoody Zantzinger
Hi Stony - Glad we arn't going crazy with this issue.

All of your info lines up roughly with ours. The problem started around Monday and has stopped periodically. We also opened a case, our case is #10532449.

Thanks,
-Woody
Stony Grunow - BreadwinnerStony Grunow - Breadwinner
Hi Woody

It's a tricky problem, as there are no error messages.

If it was a validation issue, you would get an email from Salesforce with the content of the submitted form and the validation error - so that's not it.

In theory, it's impossible to have a web to lead fail and NOT get an error message somehow. So this is an internal issue for Salesforce. I'm guessing we'll find this post filling up with other people reporting the same thing soon.

stony
Stony Grunow - BreadwinnerStony Grunow - Breadwinner
And our case number is 10511320

Salesforce - please address this! The silence is overwhelming.

If anyone else has the same issue, please file a case and post that case number here. The more orgs that have this issue, the harder it will be for Salesforce to ignore the issue and claim it doesn't exist.
Andrea Alt 14Andrea Alt 14
Looks like there is an extra HTTP header on responses that failed to generate a lead. It's called: is-processed

The HTTP result is still a 200, so it looks like success but the extea header indicates a failure.
太郎 渡邉太郎 渡邉
Hi

It is happened in my ORG.
I input same data in Web-form and send to salesforce, one case is successful, but other case is failure without notification.

I'm sorry for your inconvenience.
Does anyone know the solution?

Taro