Export Operation FAQ¶
Answers to common questions about the Export Operation, grouped by topic. For step-by-step instructions, see the how-tos; for conceptual references, see the deep dive.
Triggering an export¶
Who can run an Export Operation?¶
Triggering an export requires the Editor team permission on the source datastore. Workspace Admins bypass team-permission checks. See Permissions.
Can I export multiple asset types in one operation?¶
No. Each Export Operation captures exactly one asset type (Anomalies, Quality Checks, or Field Profiles). To export all three, trigger three separate operations.
Why doesn't my export run when I expected it to?¶
If more than 100 operations are already queued or running, new operations are rejected with 429 Too Many Requests; retry once the queue drains. Triggering a deactivated schedule on demand returns 409 Conflict. See API for the endpoint payloads and the Interactive API reference for the full response schemas.
What happens if my export is too large?¶
Large exports are no longer refused when you request them. Qualytics prepares an export in parts and stages them in the enrichment destination before writing the output, so exporting every container in a datastore at once is supported.
Safeguard limits still apply while the data is prepared (by default, 50,000,000 records and 4 GB of compressed data per export, and no single record over 32 MB). An export that exceeds one of them finishes with result = failure and the operation message names the limit. If it fails before the final write, the output from an earlier successful run is left unchanged.
If you hit a limit, cover fewer containers per run (use Specific or Tag selection instead of All) and split the export into several smaller runs. Copy each completed batch to another location before starting the next run: each run replaces the same output, even when you select different containers. See Export size limits.
Where the data lands¶
Where is the exported data written?¶
As an output container in the linked enrichment destination. The output name follows the pattern _<sanitized-datastore-name>_export_<asset>. JDBC destinations store it as a table, while DFS destinations store it in Delta format. See How It Works for examples.
Why doesn't the data appear immediately?¶
The Export Operation runs asynchronously. After the trigger call returns, the platform processes the request and writes the output. Poll GET /operations/{id} or open the Activity tab on the source datastore to follow progress.
What happens when I re-run an export?¶
The existing export output is replaced, not appended to or versioned. If you need point-in-time snapshots, schedule recurring exports and have your downstream pipeline copy the output after each successful run.
Schemas¶
What's the difference between first_asserted and last_asserted in the Quality Check export?¶
first_asserted is the earliest scan that produced a pass or fail result for the check (preserved across out-of-order partition scans, so it never moves forward). last_asserted is the most recent. Both reflect the scan start time in UTC. See Export Schema.
Why is the Anomaly export so minimal?¶
The export captures the stable identifier (uuid), container, type, status, and tags so it can be joined with the live Anomaly API for additional detail without duplicating large fields like the failed-check payload.
Field masking¶
Does field masking affect Anomaly or Quality Check exports?¶
No. Masking only affects the histogram_buckets column of Field Profile exports. See Field Masking.
How do I include unmasked values in a Field Profile export?¶
Turn on the Reveal Masked Values toggle in the Export Operation modal (visible only when the asset type is Field Profiles), or pass include_masked: true on the API request. Either requires Editor permission on the source datastore. The action is recorded in the Platform Audit.
Scheduling¶
Can I schedule recurring Export Operations?¶
Yes. Schedules support Hourly, Daily, Weekly, Monthly, and custom Cron frequencies in any IANA timezone (default UTC). See Schedule Export.
What happens when I deactivate a schedule?¶
The cron expression is kept. Reactivating the schedule resumes it without setting it up again.