---
title: Catch export filter typos before the export runs
date: 2026-09-02
description: An export filter with a typo or the wrong case now stops the export with a clear error instead of quietly exporting your whole store.
tags: ["Exports","Altera CLI"]
categories: ["Changelog"]
url: https://www.getaltera.com/changelog/2026-09-02-exports-reject-unknown-filters/
---


When you filter an export from the CLI, the API, or an MCP client, a key with a typo or the wrong case, such as `Handel` instead of `handle`, used to be dropped without a word. The export then ran with no filter at all, and the count preview showed your full store as if that were the plan. Every export now checks its filter keys before it starts, no matter where you create it.

### Fixes

- **Unknown filter keys** - an export with a filter column the data type does not have stops with error JOB008 instead of exporting everything (see [error codes](https://support.getaltera.com/en/articles/11490216-error-and-warning-codes#JOB008)).
- **Valid keys in the message** - the error lists the filter columns the data type does support, so you can fix the key without leaving the terminal.
- **Count preview** - the row count on the export screen shows the same error instead of the store-wide total.
- **Filter lookups** - run `altera ref filters <resource>` in the CLI, or call `ref_filters` from an MCP client, to see the exact keys for a data type.

Filter keys are lowercase slugs such as `handle`, `created_at`, or `status`.