Hi,
just as an idea.
What do you think about such a feature?
When working with complex process plans, it would be helpful to have the ability to set breakpoints within the system.
Such a feature would allow the execution to pause at defined stages – for example, after individual actions or fixups – enabling users to verify whether the intermediate results match expectations. Currently, the entire process plan must be executed before any results can be reviewed, which can be time-consuming and error-prone, especially with complex configurations.
Another challenge is error diagnosis: when a failure occurs, the system typically provides only a generic error message that does not reveal where in the process the issue arose. Additionally, it is often unclear which steps completed successfully and where a misconfiguration may have led to incorrect results.
An integrated breakpoint feature would not only improve efficiency during setup and testing but also significantly enhance transparency and troubleshooting.
Good question; you’re also not the first to ask for something like this, but it’s not easy to implement (in a way that would make sense).
Have you tried the “Log profile execution” feature?
I understand it doesn’t help from a timing perspective, you still need to run through the whole process plan. But it does do a very good job at showing what path was followed through a process plan, and what the intermediate results were…
Thank you for your response – it’s good to know that I’m not the first who ask for such an option.
Yes, I’ve already tried the “Log profile execution” feature.
While it does provide detailed information, it sometimes goes a bit too deep—especially with regard to the generated directories—making it harder to work with in certain cases.
The “process.log” file is helpful, but navigating through can be quite time-consuming—especially since the entire ProcessPlan has to be executed again.
Of course, I fully understand that user requests can’t always be implemented easily or quickly. It sounds easy, but putting it into practice is a different story.
The idea for this feature came to me because my (still current) workflow solution offers a similar possibility – but comes with other limitations.