Skip to main content
A
Anonymous
September 12, 2014
Question

Error getting form forwarding urls. Form not saved.

  • September 12, 2014
  • 2 replies
  • 4537 views

Hey, 

I have embedded a couple marketo forms on my site and when trying to post the forms i get this error:

error: true
errorCode: 500
message: "Error getting form forwarding urls. Form not saved."

The forms are embedded on the site using the "normal" -embed type and are set to stay on the page after submitting the form. Please help. :)
EDIT: It seems that this only happens inside our companys local network, when i try it on my own phone the forms work fine.


 
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Kenny_Elkington
Adobe Employee
Kenny_ElkingtonAdobe Employee
Adobe Employee
September 12, 2014
Hi Otto,

I'd recommend you take a look at this with your IT resource, it's like that there's an issue with your local DNS or firewall preventing some network request from executing properly.
A
Anonymous
February 10, 2016

Hi there, I feel like this is a server side error. I am having a hard time believing there is any way a local network config could cause a marketo server to return a 500 error (internal server error) with the message "Error getting form forwarding urls.  Form not saved." My suspicion is supported by the fact I have tried submitting 2 different forms from 3 different networks (my phone mobile network via tethering, home wifi, and work wifi). Same result everywhere. In addition, there was a point where it was working perfectly, and I changed nothing, and now it doesn't work. I receive this error whether I use the official JS snippet they give you (directly embedding the Marketo form in the page), or build a form myself in JS (according to the documentation) and try to submit it that way.

SanfordWhiteman
SanfordWhiteman
Level 10
February 11, 2016

Please post a link to your form embed code.

A
Anonymous
April 26, 2016

I was able to replicate this error several times by going through the following steps:

1. Open page with Marketo form as a cookied Marketo lead.

2. Delete lead in Marketo

3. Attempt to submit form (greeted with the following error)

in console:

body of response from Marketo (the decoded JSON)

4. If I refresh the page once and try again, it works fine.

However, if I switch steps 1 & 2 the error does not occur. In other words, it only occurs if the page with the Marketo form is loaded before the lead is deleted in Marketo. I'm not sure why this is. The form cannot be submitted even after waiting a few minutes; the page must be refreshed so I'm guessing it has something to do with forms2.js adding some Javascript state that has to be flushed.

Hope this is helpful to your dev team as they're debugging. Just load a form, delete the lead associated with cookie on the page you just loaded, and then try to submit the form. I highly doubt this happens often to actual leads, but it'd probably be good to understand what's going on.

Thanks!

Brian_Litzinger
Brian_Litzinger
Level 1
June 9, 2017

I too am seeing this error, but we're not using the embedded form. We're using a custom form posting to the leadCapture/save2 endpoint via Guzzle. The "Error getting form forwarding urls" part of the error message is vague and abstract and could be interpreted as an error from our server, however, the "Form not saved" part of the error is clearly an error message from the Marketo endpoint. Our server and script does not know if a form is saved or not. This does not happen every time, and happens across several different server instances in our environment. Some more detailed information about the error from Marketo would be nice to have here instead of this vague, undocumented error.

SanfordWhiteman
SanfordWhiteman
Level 10
June 11, 2017

Are you going over the rate limit of 1 form post every 2 seconds? (This limit is per source IP so when you attempt a server-side form post you are severely lowering your capacity.  The Forms 2.0 client-side API should be used instead.)

BTW this issue, as Micah encountered it, doesn't have to do with client-stored state exactly. It's that the garbage collector doesn't run on the server until the first "mismatched post" occurs. It's reasonable IMO that a post with a broken cookie (that is, a now-deleted cookie that was associated with a now-deleted lead) should not be serviced. in the absence of any other direction.

If you want to delete a lead and ensure that a cookie in a current pageview isn't broken, you should reassociate the cookie with a dummy lead on the server, then delete the lead.  Then the cookie will still exist, even though the original lead doesn't.

Terms & ConditionsAccessibility statement

Loading footer...