Hey @Tess, I’m still having this module enum input param problem w/ Retool Cloud Enterprise.
Can you confirm this fix is shipped and live? If so, the fix didn’t work.
Hey @Tess, I’m still having this module enum input param problem w/ Retool Cloud Enterprise.
Can you confirm this fix is shipped and live? If so, the fix didn’t work.
Hi @plwolfe,
Thanks for reaching out. Yes, the pr for this did ship to Cloud already. Looking at our logs of the “s.enumValues || ).map is not a function” error, the errors dropped off after we shipped the fix, but I will look into whether the issue resurfaced.
Just to double check, are you seeing the exact same “s.enumValues || ).map is not a function” error, or are you seeing something else broken with enum values?
Hey @Tess, thanks for following-up.
I’m not seeing console-level errors, just broken enum functionality in module inputs.
I have a handful of modules that have enum inputs, and they worked fine until recently. Now, however, when I try to include any module with an enum input, the dropdown of enum options is blank, preventing me from selecting from the preconfigured enum options in the module. The module input parameter also has a red warning icon next to it, and the tooltip hover message states “Selected option is no longer valid. Please choose another.”
The end result is that any module using/relying on an enum input parameter is currently completely broken. I’ve had to create new string input parameters on the modules and then refactor the modules’ code to use the string instead of enum inputs just as a workaround to keep business operations moving.
Screenshot of module input with the blank enum dropdown and the error message.
Thanks for these details! Yes, I am able to reproduce this bug
. I have informed our engineering team, and I will reach out here when we have a fix