Why is String Confusing Modules and Incorrectly Labeling Props as Mandatory When They're Set to Optional?

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

hi, i have noticed some strange behaviour today with string/ it is getting confused with the modules and then stating things that are not true. i have a workflow where the props are all showing as mandatory. when asking to change that to optional it is telling me they are already optional. not sure what updates have been made but today has been the first day where string is actually just using up my credits and giving the same answer over and over again without fixing the issue.

2

Hey , thank you for raising this issue.

We’re tracking issues on GitHub, would you mind open a new GitHub issue here. Stating your prompts and possibly your Pipedream string chat URL (only Pipedream employee can access it for debuging purpose)?

3

+1 and screenshots would be helpful too

4

thanks, i have created the issue - [BUG] - string not functioning - unable to take actions it says it has done · Issue #18021 · PipedreamHQ/pipedream · GitHub
let me know if you need more context @U05FUC30Q01