The Copper operations channel has two reports: an import error and a billing delay. The supplied records include both services, a VM error and a higher-severity import event. A broad error query can mix those signals, while an exact ERROR comparison can omit a CRITICAL record. The useful query is the one that matches the question being investigated.
Use the fixed original records to narrow the resource type, service, severity and result count. Compare the returned references with the expected evidence instead of accepting any nonempty result. The local parser implements a small documented subset: field equality, AND and severity comparisons. It cannot search a live project, apply the full Logging language or infer that a missing result means the application is healthy.
This filter includes CRITICAL and excludes the independent VM and billing events.