CSV Import Errors

You import data from Settings > Import.

File won't upload

• Wrong format: Only .csv files are accepted.
• Too large: The file must be under 1 MB.
• Too many rows: You can upload up to 200 rows at a time.

Headers not detected

The import works out the file type from one key column: monitor_url for services, severity for incidents, category for changelog posts, icon for help categories, and category_name or excerpt for help articles. Header case doesn't matter, but the type must match the product you selected. For best results, download a template under Download Templates and keep its columns.

Rows marked Err

Before you import, the preview flags rows that are missing a required value: a name for services and help categories, a title and body for changelog posts and help articles, or a title and a valid started_at for incidents. Hover over Err to see why. These rows are left out of the import.

Errors after you click Import

Other problems appear in the import result as row errors:

• Invalid status value: Values must match exactly and are lowercase, for example operational, not Operational.
• Blank value: An empty status, severity or category cell causes an error. Fill in every one.
• Invalid date format: Use ISO 8601 format, for example 2024-01-15T09:00:00Z.
• URL validation failed: Monitor URLs must start with http:// or https:// and point to a public address.
• Too many services: On the Free plan, an import that would take you past 10 services is rejected, and nothing is imported.

Rows marked Dup

The preview marks a row Dup when it matches an existing record: services and help categories by name, changelog posts and help articles by title, and incidents by title and started_at together. Matching ignores case. Choose Skip duplicates to leave those records as they are, or Overwrite duplicates to update them.