Automation optimizes scheduling, but improvements needed in error reporting and script executionIn my particular use case, for session management, it would be better if I could get a more granular view into connectivity issues to servers. Sometimes, although your flows or tasks are running as scheduled, connecting to the servers can hit a snag without alerts or error logs to check. Some servers might need patching or could be affected by network issues or latency. The workflow sometimes gets stuck without clarity on the errors. An explicit error report would be helpful, especially when the connection fails unexpectedly. It's complex to analyze problems that might arise from firewall issues or other anomalies that could hinder the flow from executing as expected. The depth of these connection challenges would benefit from better debugging capabilities. As for improvements, if Automate wasn't designed primarily for script execution, that's understandable. However, for Linux, I would prefer to see less complexity in workflows to achieve a natural completion of scripts. There are features, such as 'wait for terminal output,' that should more intuitively detect completion based on the shell prompt. Improving those aspects would make Automate more efficient for my needs. Regarding error reporting, I think Automate should offer better error reporting when connecting to servers. Currently, there are many instances where I see empty logs, indicating that, while tasks are scheduled, commands are not executing successfully. This is a significant concern, especially with critical workloads where visibility into errors is essential.
