The CW Automate Ops Console replaces direct portal monitoring for MSP operations teams managing RMM agent fleets. It combines agent inventory, patch compliance, alert feeds, script execution, and monitor trigger counts into a single always-on interface. Engineers can search, filter, and drill into any agent to see system metrics, run remote commands, and view the event timeline without switching tabs.

The console uses a three-column layout: left (API health, patch donut, client breakdown), center (agent inventory table + 24h check-in chart), and right (script runner, alert feed, top monitors). A slide-out drawer provides full agent detail and remote command output.

CW Automate uses a two-step token-based auth. First, POST credentials to get a Bearer token. Then include it in all subsequent requests. The token format differs from standard Bearer — it uses the CWA token= prefix in the Authorization header.

The frontend calls /api/automate/*. The proxy injects auth headers and forwards to the CW Automate server. Token refresh should be handled server-side with a cached token renewed before expiry.

• Provision a server-side proxy (Node.js/Express, Cloudflare Worker, or equivalent)
• Set environment variables: CWA_USER, CWA_PASS, AUTOMATE_URL (e.g. https://your-server.com)
• Implement token acquisition: POST /automate/api/v1/apitoken → cache CWAIISToken
• Implement token refresh logic (before 24h expiry)
• Implement proxy route: /api/automate/* → AUTOMATE_URL/automate/api/v1/* with Authorization: CWA token=<token>
• Handle pagination: /computers with 100+ agents requires looping ?page=N&pagesize=100
• Set CORS headers to allow requests from the console’s serving origin
• Test GET /api/automate/computers → verify agent count matches Automate portal
• Test GET /api/automate/alerts → verify alert list matches open alerts in Automate

• Open dashboard-stack-cw-automate.html and locate const DEMO = true near the bottom of the script block
• Set const DEMO = false
• In apiFetch(), uncomment the production block (8 lines starting with try {)
• Comment out (or delete) the demo fallback return new Promise(resolve => setTimeout(...)) block
• Reload — the header label should show “Live” instead of “Demo”
• Verify agent count in the Total Agents KPI matches the Automate portal
• Verify the client breakdown bars reflect real client names
• Test clicking an agent row → confirm API calls section in drawer shows real latency
• Test Ack on an alert → confirm the POST call returns 200/204 from the proxy

Cause: loadDashboard() or refreshAll() was not called, or the agents array was empty when rKPI() ran.

Fix (demo): Check browser console for JS errors. Confirm buildAgents() returns a non-empty array. Verify DOMContentLoaded listener calls loadDashboard().

Fix (live): Confirm the proxy returns valid JSON from /api/automate/computers. Check that the response has a results array.

Cause: Active filter plus search text yields no matches, or agents array is empty.

Fix: Click the “All” filter chip. Clear the search box. Call renderAgents() from the console to verify the agents array is populated. In live mode, log agents in the console after a refreshAll() call to confirm data shape matches expectations.

Cause: The CW Automate alert ID format from the mock (ALT-3000) differs from real Automate alert IDs (numeric). Or the proxy is not routing POST /alerts/{id}/ack correctly.

Fix: Verify the alert object from GET /alerts includes an id field (integer). Update the alert rendering to use the real ID. Confirm the proxy routes POST /api/automate/alerts/{id}/ack → POST /automate/api/v1/alerts/{id}/ack.

Cause: In live mode, the script ID from the select dropdown (value="1" through "8") are mock IDs that do not correspond to real scripts in the Automate instance.

Fix: In production, populate the script dropdown from GET /automate/api/v1/scripts and use real script IDs. The target computer must also be selected from real agent IDs from the agents array.

Cause: Bearer token is expired, or the Authorization: CWA token= header format is wrong (standard Bearer prefix does not work with CW Automate).

Fix: Re-acquire the token via POST /automate/api/v1/apitoken. Confirm the header format is exactly CWA token=<tokenValue> (note: not Bearer). Implement token refresh in the proxy before the 24h expiry.

Cause: openAgentDrawer(id) could not find the agent in the agents array (ID mismatch), or the drawer/overlay elements are missing from the DOM.

Fix: Confirm agents.find(x => x.id === id) returns a truthy value. In live mode, agent IDs from the API must be stored as numeric values matching what is passed in row onclick. Check browser console for “Cannot read properties of undefined” errors.

Cause: startAutoRefresh() was not called, or the DOMContentLoaded event did not fire (e.g. script was blocking).

Fix: Confirm the script block ends with a document.addEventListener('DOMContentLoaded', ...) listener that calls both loadDashboard() and startAutoRefresh(30000). Manually call refreshAll() from the browser console to test the data cycle in isolation.

Cause: mPatches(agents) returned all zeroes (all agents have the same patch state), or total is zero causing a divide-by-zero in percentage calculation.

Fix (demo): Verify the PATCH constant array contains all four values and buildAgents() assigns random patch states. Confirm agents is not empty. Fix (live): Confirm the proxy returns patch records from /patches with a valid status field matching current|pending|critical|outdated.