---
title: 'ARCE0003: An @observe query has neither :watch nor :topics'
editUrl: https://github.com/Cratis/Arc.Elixir/edit/main/Documentation/code-analysis/ARCE0003.md
description: ARCE0003 warns when an Elixir @observe query declares neither :watch nor :topics, so it answers once per subscription and never pushes an update.
lastUpdated: 2026-11-14T00:00:00.000Z
---


**Kind:** module. **Default severity:** warning.

## Rule

An `@observe` query re-runs, and pushes the new result to its subscribers, when something it watches changes: the Chronicle read models in `:watch`, or the `Arc.Notifier` topics in `:topics`. With neither, nothing ever triggers it, so it answers once per subscription and then stays silent.

## Why it matters

The client subscribes and gets a first result, so it looks as if it works. The data then goes stale on screen, and the cause is easy to miss in review.

## Bad

```elixir
@observe many: true
def live_authors(_args, _ctx), do: Chronicle.all(MyApp.Authors.Author)
```

## Good

Say what changes it:

```elixir
@observe many: true, watch: [MyApp.Authors.Author]
def live_authors(_args, _ctx), do: Chronicle.all(MyApp.Authors.Author)
```

or, for data that something else announces:

```elixir
@observe many: true, topics: ["authors"]
def live_authors(_args, _ctx), do: Chronicle.all(MyApp.Authors.Author)
```

## How to fix

- Add `watch:` and/or `topics:` to the `@observe`.
- If the data never changes while subscribed, use `@query` instead.

## Related

- [Queries and read models](/arc/backend/elixir/queries/)
- [Observability](/arc/backend/elixir/observability/)
