# Only One Scheduled Osquery Query Pack Runs in Agent Policy

**URL:** <https://discuss.elastic.co/t/only-one-scheduled-osquery-query-pack-runs-in-agent-policy/388792>\
**Category:** Metrics\
**Tags:** elastic-stack-monitoring\
**Created:** [July 26, 2026, 12:33pm UTC](https://discuss.elastic.co/t/only-one-scheduled-osquery-query-pack-runs-in-agent-policy/388792 "2026-07-26T12:33:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Viktor\_Movita](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/viktor_movita/32/135707_2.png) [@Viktor\_Movita](https://discuss.elastic.co/u/Viktor_Movita)\
**Post date:** [July 26, 2026, 12:33pm UTC](https://discuss.elastic.co/t/only-one-scheduled-osquery-query-pack-runs-in-agent-policy/388792/1 "2026-07-26T12:33:00Z")

</div>

Hello,

I am using **Elastic Agent 8.19.14** and collecting **systemd unit** information through the **Osquery Manager** integration.

Recently, I have encountered an issue where, if I configure **two query packs** within the same Agent Policy, only one of the packs runs while the other does not.

The queries in both packs:

- Are configured as **Snapshot** queries.

- Have different query IDs.

- Run at different intervals.

- Are visible in the **Inspect** view.

- Execute successfully when run manually as **Live Queries**.

However, when scheduled through the query packs, one pack consistently runs while the other does not. On the affected agent, I can see logs indicating that **0 events were sent to the index** for the queries that do not execute.

Is this a known issue in Elastic Agent 8.19.14 or Osquery Manager? What could cause one scheduled **Snapshot** query pack to stop executing while another query pack in the same Agent Policy continues to work?

Any guidance on additional logs or diagnostics I should collect would be appreciated.
