ConnectWise Automate script runs successfully on demand but fails under scheduled automation

Issue Summary

This article covers a ConnectWise Automate issue where a script or automation works when run manually but fails or silently does nothing when executed on schedule. Use the path below to isolate context, permissions, and scheduling dependencies before duplicating or rewriting the script.

Symptoms and Scope

• The same script succeeds when launched manually from the console but fails under its normal scheduled workflow.
• The failure may affect one client, one group, or all endpoints using the same automation.
• A known-good manual run provides a baseline for what the script should do when context is correct.

Tier I: Basic Checks

1. Confirm the schedule, target group, and trigger conditions are actually matching the endpoints at the expected time.
2. Capture the exact difference between the manual run context and the scheduled run context, especially user, credentials, and working directory assumptions.
3. Check whether the target endpoint was online, out of maintenance mode, and eligible to receive the automation when the schedule fired.
4. Review the most recent run history before making changes so you do not erase useful evidence.

Tier II: Admin Investigation

1. Compare execution context, permissions, variables, and dependencies between manual and scheduled runs.
2. Review Automate logs for suppressed prompts, missing files, timing assumptions, or agent-side execution restrictions.
3. Test the same script with minimal logic under schedule to prove whether the failure is script content or scheduling context.
4. Correct the narrow dependency that breaks unattended execution instead of rewriting the whole automation flow.

Tier III: Advanced Remediation

1. Rework the script for true unattended execution only after proving the failure is not due to policy timing or missing prerequisites.
2. If many clients are affected, check for shared probes, plugin updates, or central scheduling issues rather than endpoint-specific causes.
3. Escalate to deeper Automate diagnostics if the scheduler itself appears to dispatch incorrectly across different automations.
4. Validate the final fix by confirming repeated scheduled success, not just one manual run.

Escalation Guidance

• Escalate when production automations, patching, onboarding, or monitoring workflows depend on the failing schedule.
• Provide schedule definitions, script history, execution logs, target groups, and the manual-vs-scheduled comparison evidence.
• State whether the problem is context, timing, permissions, variables, agent behavior, or scheduler reliability.

Prevention and Documentation

• Document how the script was hardened for unattended use so future automations follow the same pattern.
• Update script standards to avoid interactive assumptions and unstable working-directory logic.
• Add monitoring for failed scheduled runs if the automation is operationally critical.