Form Submit undocumented status

[James_Gilliland]

When submitting a form to the lead/submitForm I got a failure because it returned response status of 'warning'. There's no documentation of what this status means or how to handle it. Also, not being documented as an allowed value breaks automated code generation tools which, if you'll pardon the gripe, has been a pretty consistent problem for over a year trying to get switched to this from the old API.

[Jo_Pitts1]

@James_Gilliland,

can you provide the URL that the form is sitting on please?

Cheers

Jo

[James_Gilliland]

Not really, I'm developing against the REST API for an opensource library. I'm not looking to fix a form so much as documentation so anyone using the library can handle the situation correctly.

[SanfordWhiteman]

Do you mean the $.warnings array in the response? Can you provide a specific response JSON example?

[James_Gilliland]

Seems related but no, the status field. The documented values don't include "warning" but I'm getting it.

(string) = ['created', 'updated', 'skipped']
string Enum: "created", "updated", "skipped"

Can I trust this means the values are saved? Can we get documentation on what situations would cause this?