# Automation Workflow Issues

> Fix an Automation workflow that does not run on schedule, targets the wrong endpoints, or does not update apps and drivers.

Source: https://docs.capaone.com/capaone/troubleshooting/automation-workflow-issues/  
Product: CapaOne — a separate CapaSystems product; do not apply this page to any other.

## Problem

An Automation workflow is not running as expected — either it is not executing on schedule, it
is not targeting the right endpoints, or it runs but does not produce the expected result (apps
or drivers not being updated).

## Solution

Go to **Windows → Automation** and locate the affected workflow.

### 1. Check the workflow is enabled

The **Enabled** toggle must be on for a scheduled workflow to run. If the toggle is off, the
workflow is saved but will not execute. Enable it and wait for the next scheduled run.

### 2. Check the schedule

The Schedule column shows a human-readable description of when the workflow runs (for example,
"At 22:00, on day 1, 2, 3... of the month"). Verify the schedule matches when you expect the
workflow to run. If the schedule is set to overnight hours and you are checking in the morning,
confirm the workflow ran by checking the **Last run** timestamp.

If the Last run shows **Never**, the workflow has not executed yet. This is expected if it was
recently created and the scheduled time has not occurred yet. You can run it immediately using
**Options → Run now** without waiting for the schedule.

### 3. Check the filter (targeting)

The **Filter** column shows which endpoints the workflow targets. "All" targets every endpoint
in the organization. If the filter is set to a specific group, only endpoints in that group
receive the workflow actions.

If an endpoint is not being updated:
- Confirm the endpoint is in the targeted group.
- Confirm the endpoint is online and checking in (Windows → Endpoints, check Last check-in).

### 4. Check the workflow actions

Click the workflow name to open the flow board. Verify:
- The correct actions are connected (install, update applications, update drivers, etc.).
- The actions are connected to the Filter block — disconnected action blocks will not execute.
- The applications or drivers referenced in the actions still exist in CapaOne and are not
  deprecated or removed.

### 5. Run on demand to test

Use **Options → Run now** to trigger the workflow immediately without waiting for the schedule.
This is the fastest way to test whether the workflow logic works correctly. After running, check
the Last run timestamp and status.

### 6. Check the endpoint's application status

After a workflow runs, go to the endpoint detail page and check whether the targeted apps have
been updated. Allow a few minutes for the agent to process the workflow and report back.

## Good to know

- **Scheduled workflows can also run on demand** — using Run now does not affect the scheduled
  execution. The workflow will still run on its next scheduled time after the on-demand run.
- **On Demand workflows** — workflows created as "On Demand" never run automatically. They must
  be triggered manually using Run now or from an individual endpoint's detail page.
- **Disabled workflows retain their configuration** — disabling a workflow does not delete it.
  Re-enable it when you want it to run again.
- **A workflow with status "None"** has not run since it was last modified. This is expected for
  newly created or recently edited workflows.