Can Start-Stop-Automation Scripts be Modified to Reflect Failure Status upon System Startup Issues?

Hello,

Is there a way to adjust Start-Stop-Automation scripts so that they accurately report a "failed" status in situations where the system fails to start? Currently, the scripts consistently conclude with a "completed" status, even when the system encounters issues during startup.

Given that we rely on monitoring tools to track the completion status of automation accounts, it's imperative that the scripts reflect the true outcome of the automation process. By ensuring that failures during system startup are appropriately flagged, we can improve the reliability of our automation processes and enable our monitoring tools to effectively detect and respond to any issues.

Are there any recommendations or modifications that can be made to achieve this goal?