Workflow Executions

[Hemanth-Bethu]

1. Is there a way to view execution details similar to Apache NiFi's execution logs — specifically, the ability to trace errors at the node level and inspect inputs, outputs, and parameters?
2. Would it be possible to implement node-to-node navigation similar to NiFi’s UI? That kind of visual guidance would be extremely helpful.
3. Incorporating versioning or undo/redo capabilities would be a major advantage, especially since mistakes can happen easily during configuration or design.
4. Also good to introduce flow type for asynchronous executions, like que job.

Also, I’m following your videos — they’ve been really helpful. Thanks!

[yonitjio]

Thanks for your comment! I'm not too familiar with Apache NiFi myself, but I agree that many of the features you mentioned are common across node-based UI systems.

When I started the Nuido experiment, I didn’t have a specific feature set in mind. It was mostly a way to explore and learn both the Owl framework and the general design of node-based interfaces. I've been iterating based on whatever use cases or ideas come up along the way, rather than following a structured plan.

Regarding execution logs: the simplest approach right now is to manually add a logger to each node. A more integrated logging mechanism would likely require changes to the base node class, which would affect the entire system. Ideally, something like a simulation or dry-run mode would be great to have, but that’s a bit out of scope for this experiment at the moment.

As for "node-to-node navigation," I’m not entirely sure what that entails—feel free to clarify! In the meantime, I do plan to gradually introduce better navigation features such as multi-selection, keyboard shortcuts, and more.

I completely agree that features like versioning, undo/redo, and asynchronous execution are essential for a production-level app. Hopefully, as the project matures, I’ll be able to incorporate some of those as well.

Thanks again for taking the time to look at the repo and share your thoughts!

[Hemanth-Bethu]

Would it make sense to start a list of features and improvements in the form of a roadmap? That could help bring clarity and structure to the evolving feature set. A few ideas:

Trigger Timing & Stability
When nodes execute during create or edit triggers in Odoo, they may interfere with the standard flow—especially under load. If the node's execution is synchronous and the flow is heavy, it could result in unexpected failures or incomplete transactions. In an asynchronous environment, we can track and re-execute from the point of failure.

Node-to-Node Navigation & Debugging
Currently, when a flow fails, there's no clear way to trace the input/output or the point of failure—it just fails silently. In real-world use, especially with dynamic data, this makes debugging quite difficult. Having a way to inspect node inputs/outputs post-execution would be extremely valuable.

UX Inspiration from Apache NiFi
I’ve attached a screenshot for reference. If you get the chance, I highly recommend trying Apache NiFi’s UI. It sets a strong example for intuitive node-to-node visual navigation and flow understanding. Also Currently you can't left or right in nifi you can grab emty area of background and drag left right and top.

[yonitjio]

Thanks for the thoughtful feedback — I really appreciate your input!

It would definitely be great if Nuido supported the features you mentioned. However, as I mentioned earlier, Nuido is primarily intended as a learning tool, not for production use.

Please understand that this project is something I created to help others learn and to support content for my YouTube channel. I'm the only one working on both the repo and the channel, so building a fully production-ready system isn't my main goal at the moment.

Regarding the trigger nodes: they are essentially a simplified version of Odoo's own automation logic from the base_automation module. I understand your concerns, and I agree that there's room for improvement, but I currently don't have plans to heavily modify that part.

For debugging and execution tracing, I’ll look into adding basic logging for each node — that should help at least with visibility during development.

As for canvas navigation: you can move around by right-dragging on any empty space. More details can be found here:
nuido_ui.js#L181

Thanks again for taking the time to explore Nuido and share your thoughts!

[Hemanth-Bethu]

Thanks for your comment.
If traceability is implemented, it will greatly aid in development.