When selecting what data to include in your data product, the maximum allowed individual file size is 1.5GB and the total size of all file patterns cannot exceed 50GB.

Crux does not support viewing the progress of a pipeline run. You may view the Health Dashboard to see timestamps of when we retrieved, processed, and delivered data to your destination(s). If your next run is in the future, you will need to wait until the next scheduled run occurs before seeing your dataset in the Health Dashboard.

Crux does not support making edits to the dataset spec (YAML file) within the app. Please see the cruxctl guide on how to manage your dataset spec from the CLI tool.

Testing deploys currently follows the same delivery paradigm as delivering to a production destination. You will see your test deploys appear in the Health Dashboard based on the configured schedule. This is a known limitation of mixing test and production deliveries in the same dashboard. In the future, we will display test results in the Event Console of the data product in My Data.

Crux does not support delivery of backfill data at this time; we only support delivery of ongoing data.

Crux does not support unzipping archives within archives (.zip files inside of .zip file patterns).

When delivering as a RAW format, the delivery will only be successful when selecting a file-based destination (SFTP, FTP, GCS, S3 or Azure Blob).

The Sphere by Self-Service product does not support database shares for destinations; this feature is only available for the Sphere by Managed offering.

Crux does not support displaying dataset health statuses for datasets with intraday schedules.

Crux does not support displaying a data's "as-of-date" showing the date pertaining to a data's freshness. The Health Dashboard displays any data arriving by an expected deadline, regardless of the as-of date

Crux does not support table-level observability with a breakdown of files within the dataset that are healthy/unhealthy.

Crux does not support viewing logs for dataset failures at this time. Please see the cruxctl and Troubleshooting Guide on how to view logs to better understand dataset issues.