Quick update: we’ve prioritized this bug and is currently sitting as one of the next tickets to be picked up by an engineer. No timeline yet, but hopeful for a relatively speedy resolution since you’ve confirmed it’s something that was added in 0.216.0 (not some existing, difficult to pin down bug).
Will keep this thread updated; and hopefully get you back on the latest version ASAP @shrey-42 .
Just checked. The 2nd case seems to have fully resolved now.
The first one, partially. Although, the formatting is now proper, for some reason, the ‘preview value’ underneath the input field is completely dynamic (updating in real-time), as opposed to being set to a fixed value at the time of the execution of the node. See:
Hi @shrey-42, thanks so much for checking in. Do you think that the preview being in real-time is an issue or actually good? I can def. see that it might be confusing but also see that it’s the correct behavior because the value would be updated once you execute again. Would love to hear your thoughts.