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] Flyteconsole: status of gate nodes does not update without refresh #3524

Closed
2 tasks done
jsonporter opened this issue Mar 23, 2023 · 1 comment
Closed
2 tasks done
Assignees
Labels
bug Something isn't working Epic: Signaling Signal support, gate nodes, and HITL workflows untriaged This issues has not yet been looked at by the Maintainers
Milestone

Comments

@jsonporter
Copy link

Describe the bug

Currently in flyteconsole when a user interacts with a signal/gate node (ie, approves, rejects or provides a value, etc) the workflow continues appropriately however the UI doesn't update the state of that node from paused --> ${some phase}. However, if the user refreshes the page the phase is correctly labeled.

The correct behavior is that the phase displayed should always be up-to-date without a page refresh.

Expected behavior

Gate nodes should update without a page refresh after a user interacts and lets the node proceed.

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@jsonporter jsonporter added bug Something isn't working untriaged This issues has not yet been looked at by the Maintainers Epic: Signaling Signal support, gate nodes, and HITL workflows labels Mar 23, 2023
@jsonporter jsonporter added this to the 1.5.0 milestone Mar 23, 2023
@cosmicBboy cosmicBboy modified the milestones: 1.5.0, 1.6.0 Apr 20, 2023
@jsonporter
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Epic: Signaling Signal support, gate nodes, and HITL workflows untriaged This issues has not yet been looked at by the Maintainers
Projects
None yet
Development

No branches or pull requests

3 participants