Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: flow_input reverts when loading previous run data through "Test flow" when clicking javascript expression #5187

Closed
zach-wire3 opened this issue Jan 31, 2025 · 4 comments
Assignees
Labels
bug Something isn't working release: 1.456.0

Comments

@zach-wire3
Copy link

Describe the bug

Prior to v1.454.0, I used to use "Test Flow" to populate data the "Input" block with test data from prior runs while developing flows. Now, with the new history view, the data seems to revert back to empty values whenever I attempt to use it in a script input.

To reproduce

  1. Go to flow editor
  2. Click on a script/block if one is not highlighted already
  3. Click on "Test Flow" at the top of the screen
  4. Use the new history viewer on the right side of the form and select a prior run
  5. Visually confirm that form is filled out with prior run data
  6. Click on "X" at the top left or empty space to the left of the test flow to return to flow editor without clearing data
  7. Visually confirm that flow_input populated with test data in data connection box (the box right below "Search prop...")
  8. Attempt to connect data to script/block
  9. Witness pre-populated values disappear to nothing

Expected behavior

Just like in version prior to v1.454.0, I want the "Test Flow" inputs to populate the "Input" block's data that gets referenced during the creation/development of a flow. This allows for streamlined usage of prior run data to not only help with development of flows, but is useful when debugging errored flows.

Screenshots

No response

Browser information

Firefox 134 & Chromium 128

Application version

CE v1.455.1

Additional Context

No response

@zach-wire3 zach-wire3 added the bug Something isn't working label Jan 31, 2025
@rubenfiszel
Copy link
Contributor

I can't reproduce, but also not exactly sure what you mean by:

Attempt to connect data to script/block

Would you have a little video you can share?

@zach-wire3
Copy link
Author

Absolutely!

Screencast.from.01-31-2025.11.30.55.AM.webm

@rubenfiszel
Copy link
Contributor

Fixed on very latest, thanks for the report

@zach-wire3
Copy link
Author

Can confirm, issue has been fixed. Thank you very much for the quick turn around!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working release: 1.456.0
Projects
None yet
Development

No branches or pull requests

2 participants