# Form completing without all information completed

**URL:** <https://community.feathery.io/t/form-completing-without-all-information-completed/297>\
**Category:** Support\
**Created:** [November 24, 2023, 3:35pm UTC](https://community.feathery.io/t/form-completing-without-all-information-completed/297 "2023-11-24T15:35:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrew](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andrew](https://community.feathery.io/u/andrew)\
**Post date:** [November 24, 2023, 3:35pm UTC](https://community.feathery.io/t/form-completing-without-all-information-completed/297/1 "2023-11-24T15:35:25Z")

</div>

Hi,

I have a form that is basically a 15ish question set of multiple choice questions with 4 fill-in-the blank answers. I have my buttons on the fill in the blank set to only be available when the text fields have information, but sometimes 25%-30%) of the time when a user is abandoning the app the form is registering as “completed” rather than “partial” so under my results it reads as “completed - 4 fields” rather than “Partial - 4 fields”, the issue comes then because it is trying to force through a zapier link into our CRM without a first name or contact information. Any help would be appreciated.

---

<div class="post-metadata">

**Author:** ![peter](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.feathery.io/peter/32/7_2.png) [@peter](https://community.feathery.io/u/peter)\
**Post date:** [November 24, 2023, 8:24pm UTC](https://community.feathery.io/t/form-completing-without-all-information-completed/297/2 "2023-11-24T20:24:11Z")

</div>

@jay will be able to help take a look here

---

<div class="post-metadata">

**Author:** ![jay](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@jay](https://community.feathery.io/u/jay)\
**Post date:** [November 27, 2023, 2:49pm UTC](https://community.feathery.io/t/form-completing-without-all-information-completed/297/3 "2023-11-27T14:49:25Z")

</div>

Hi Andrew, we added additional logging to investigate. Will fix this ASAP. Thanks!
