Somehow forms are sometimes allowed to submit without required field

Support
21

@peter Still seeing this error on occasion, but much less overall

22

i’m hoping the connectivity fix we’re putting in will fix the rest of them!

23

Unfortunately we are seeing this still in production. It seems less frequent than before but still happening so key information isn’t being captured in our onboarding flow

24

We haven’t launched the connectivity fix yet – will LYK once we do!

2 Likes
25

Hey @peter! Any update on this one?

26

Should be out within a week or two cc: @eric

27

@peter @eric any update here?

28

it’s in progress. we’ll let you know when it’s out

29

@peter I hate to nag on this, but almost every other day, we get notified of warnings/errors on this which means we are missing the data we intend to collect.

I just want to have our expectations set appropriately. Is this something that will be resolved within the next month?

30

the change will be out within the next week or two. i can’t guarantee it will fix this issue, but that’s our running hypothesis

31

@peter How can we get more attention on this to get a full fix? As far as we know the issue isn’t caused by how we’ve integrated but something strictly withib feathery itself. If this is wrong please let me know.

We first reported this 4 months ago and its created a situation that we cannot rely on feathery for critical workflows since can’t guarantee we will get information when we expect. For example we’ve thought of ways to use feathery for users to specify critical account setup preferences. If we will get null values for that situation like we see for their names in our onboarding surveys now, this is a no go for obvious reasons.

Given this, it puts feathery in a weird spot with more limited utility than we originally planned.

32

The change is in code review right now — it will be out soon.

33

This change is live in our latest library version (2.0.423)

34

Unfortunately we are still seeing errors periodically with missing fields in submissions.

One thing new we are seeing though since the new sdk is that in addition to missing required values we are sometimes seeing errors due to header values missing

Error code: 400
Frequency: 1
Sample error message:
{“response”: “{“error”:“param is missing or the value is empty: feathery-webhook-auth\nDid you mean? feathery_form_name\n feathery_user_id\n format\n cap.onboarding_how_did_you_hear_about_us”}”, “payload”:

35

I’d recommend you use something like a session recording tool to try to get more context on what’s going on during these sessions.

We’ll probably need more context on what this header value missing issue is

36

@peter The feather-webhook-auth is a static value that we have setup in the webhook integration:

image
image1044×1418 116 KB

So there shouldn’t ever be a case this isn’t included. Given it’s at the integration level within the form config, I think this means if it’s missing it’s a bug within feathery itself and not our code?

Given the missing values (this new header missing periodically, or first and last name), it’s not realistic for us to do session recording for this. It’s happening say a dozen times a day, but we have thousands of signups going on.

37

We probably only need one recording of a flow that triggers this error to verify what’s going on. We won’t be able to help further otherwise since we don’t know what’s causing this issue on your end, and we haven’t gotten other reports of this issue.

Also it woudl be helpful for you guys to log the payload on your side and let us know what you’re collecting that triggers the 400. Webhooks are sent from our backend so should have minimal correlation with SDK changes, and the code passing the header config to the webhook call was not changed at all

38

@peter the 400 is due to it missing required fields (first name, last name) or the header field feathery-webhook-auth. Correct me if I’m wrong, but the payload on our side would just show one or more of those are missing (whcih you can see in the error response I recently showed)

“response”: “{“error”:“param is missing or the value is empty: feathery-webhook-auth
39

I would like to verify that the header field is actually missing, and if so what the payload looks like since that may offer additional info as to what’s causing it

40

fyi we’ve made some more udpates that potentially fixes your data issue, if you upgrade to the latest version