# Strange value being filled in dropdown selection?

**URL:** <https://community.process.st/t/strange-value-being-filled-in-dropdown-selection/676>\
**Category:** Advanced Uses\
**Tags:** workflows\
**Created:** [August 25, 2023, 4:20pm UTC](https://community.process.st/t/strange-value-being-filled-in-dropdown-selection/676 "2023-08-25T16:20:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cduval04](https://avatars.discourse-cdn.com/v4/letter/c/bc79bd/32.png) [@cduval04](https://community.process.st/u/cduval04)\
**Post date:** [August 25, 2023, 4:20pm UTC](https://community.process.st/t/strange-value-being-filled-in-dropdown-selection/676/1 "2023-08-25T16:20:18Z")

</div>

![image (24)](https://canada1.discourse-cdn.com/flex030/uploads/process_street/original/1X/67aa0699fdc4fee2910146d81086c1b528b00427.png)

We have a behavior whereby a string of jibberish appears as the value in a dropdown selection on the completed version of a form. When one goes to fill out and/or edit the form there is no such value, only the choices we added to the dropdown. Here’s the the screenshot of the other form (the forum only allows one picture attachment) [Screenshot by Lightshot](https://prnt.sc/0CVpbrOJ69GM)

We’ve seen this occur twice so far, with 2 different forms.  
Both were dropdown questions, both were required, both had hide logic applied to them and both had automations to send a slack notifications attached to their task number. Anyone ever seen anything like this before?

---

<div class="post-metadata">

**Author:** ![Tarik](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.process.st/tarik/32/147_2.png) [@Tarik](https://community.process.st/u/Tarik)\
**Post date:** [August 29, 2023, 12:10pm UTC](https://community.process.st/t/strange-value-being-filled-in-dropdown-selection/676/2 "2023-08-29T12:10:54Z")

</div>

hi @cduval04 and welcome to the community! Could you please email us directly at support@process.st

Are you using the Slack app by any chance? We did have an bug that was causing this behaviour with users using the slack app but that was resolved yesterday.

Please let us know if you are still experiencing this issue.

Thanks  
Tarik