Replies: 4 comments
-
Interesting. Was this just after you opened or restarted the app? |
Beta Was this translation helpful? Give feedback.
-
It was soon after a restart. |
Beta Was this translation helpful? Give feedback.
-
I can't say for sure, without more info. What could have happened is the local state refreshed without refreshing the UI, essentially creating a mismatch between the entities that the console receives updates about and the entities that are visible on screen. I'll put on the board to see if we can validate one way or the other in the latest release. Thanks! |
Beta Was this translation helpful? Give feedback.
-
@1800joe Mildly interesting here is the NodeNotFoundError is for a nonexistent Cloud Organization - NOT the Workshop Organization ID. Right now I'm not aware of a circumstance where the Workshop Organization would be accidentally queried for as a Cloud Organization, but it appears there might be a lingering edge-case here. I'll keep an eye out for this issue. Let me know if anyone comes across a reliable way to reproduce. |
Beta Was this translation helpful? Give feedback.
-
After clicking start new Deployment and selecting a previous Build to deploy
Beta Was this translation helpful? Give feedback.
All reactions