3.75.14 workflow cross contamination bug

App Building
1

This one will take some explaining.
if i create 2 functions in a workflow, lets call them a and b.
they both are rest api resource functions and will call different post api endpoints.

a:
i create a key called codeId and a value of 12

b:
a key called codeId miraculously appears with a value of 12

b:
I delete the key called codeid

a:
the key called codeId has now completely vanished

it seems since this upgrade to 3.75.14 that the functions have in some way become entangled, whatever i put as key/value pairs in one of the functions, appears in the other and vice versa.

I have tried deleting and recreating the functions, i have tried creating one function then duplicating it, always the same, The functions are entangled.
If i get time, I will upload a video showing the mysterious Retool workflow entanglement

3

Hi @peter.b,

Thanks for reaching out about this! It looks like this is a bug that our team is working on.

From the other reports, it sounds like if you have 2 (or more) REST API functions in a workflow, clicking between them will show the same key values even though they are different. It does not affect what is actually sent in the query. Is that what you're seeing? We've also seen that if you refresh the page and open the second function editor first, you'll see the expected headers.

Just want to make sure we're looking at the same bug! Don't want to undermine how tricky this makes troubleshooting.

I will post here with any updates I hear internally