Anyone else experience corrupt parameters on WFs from MCP generations? My workaround is to create a new WF and copy everything from the bugged one to the new one. Anyone any idea whats happening?
I’ve had one with a bunch of “autofix” errors where I had to click through 20 actions, but it didn’t change anything in the action itself. Outside of that one time, no. What model are you using? I suggest 5.5 High+.
Parameter NaN looks like a parameter of a data type that doesn’t exist that was present in another app the workflow was copied from.
I know that is not case here as you’re using MCP, but perhaps the workflow got created before the new data types were actually created, where MCP expected to create a data type, had not run that process and created the workflow before data types created.
What was the expected data for those parameters? Were they option sets, custom data types or api objects or plugin data types.
Could be a data type from a plugin that didn’t get installed?
Usually when a workflow gains a new optional parameter not originally present but the workflow already in use in areas of app, so when adding new optional parameter bubble makes you click through each area that workflow is ran.
I’m using opus 5.5 medium
It was a existing data type that I created before using the MCP so nothing strange there, the other issue is that it silently fails, there are no issues detected by Bubble
Can you try with High?
Same here - I couldn’t edit it to correct it either (needed to delete and recreate). It was created by Claude 5.5 High effort.
had the same issue a couple of times. what helped was not trying to do everything in one MCP prompt — like create data types in one go, check they look right, then do the workflows separately. seemed to cut down on those ghost parameters. doesn’t fully fix it though, some workflows still come out broken and you gotta delete and redo them. would be nice if Bubble at least flagged these instead of silently failing.