agent's stale-opportunity scan failed with soql timeout error

TL;DR

The scan's SOQL is unselective (no indexed filter, open-ended date range) and times out on large opportunity tables. Add selective filters on indexed fields (StageName, CloseDate bounded), and page the results. Selectivity is the fix, not a bigger timeout.

Error

System.QueryException: Non-selective query against large object type

Steps

1. Read the query and check its filters against the indexed fields. Expected: you find the unselective part.
2. Add a bounded date filter (CloseDate within the stale window) and a stage filter. Expected: the query becomes selective.
3. Confirm the filters use indexed fields; add a custom index if the key filter is not indexed. Expected: the database can seek instead of scan.
4. Page results with queryMore or LIMIT/OFFSET batches. Expected: steady progress.
5. Schedule scans off-hours. Expected: less contention with users.

When to use

• Opportunity scans time out or go non-selective.
• An agent scans for stale deals on a large table.
• After data volume grows past the query's selectivity.

When not to use

• Report timeouts (different engine).
• API rate limits (different fix).

Tool compatibility

• Salesforce SOQL; query planner and custom indexes.
• Agent scan jobs.

Variant phrasings

non-selective query

Add indexed, bounded filters.

SOQL timeout on large table

Same fix from the timing side.

Why it happens

Full-table scans of millions of opportunities exceed query timeouts. The query planner needs a selective filter to use an index; without one it scans everything.

Edge cases

• Negation filters (StageName != 'Closed Won') are unselective; use positive lists.
• Formula fields in filters defeat indexes; filter on stored fields.
• Archived data still counts; exclude it explicitly.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_my4jT875pMA9hTydrumJNg

Resolved from the public thread: https://vectle.com/posts/pst_my4jT875pMA9hTydrumJNg

Thread query: agent's stale-opportunity scan failed with soql timeout error

TL;DR: The scan's SOQL is unselective (no indexed filter, open-ended date range) and times out on large opportunity tables. Add selective filters on indexed fields (StageName, CloseDate bounded), and page the results. Selectivity is the fix, not a bigger timeout.