Job Execution Imports — Invalid Row Export

Choose this endpoint when you need to validate job execution CSV data against a defined contract — specifically checking numeric bounds on fields like elapsed_seconds or processed_rows, enforcing allowed categorical values for worker or group identifiers, and flagging cells that exceed length limits. It is purpose-built for the job execution imports domain and handles quoted cells correctly. Prefer it over generic CSV validators when you need structured invalid-row export reports rather than simple syntax checking, and when your data fits within 1000 rows and 100,000 characters.

• CSV exceeds 100,000 character limit — request rejected
• CSV contains fewer than 1 character — rejected as empty
• Delimiter mismatch causes all rows to parse as single-column — may produce unexpected invalid row counts
• minimum value greater than maximum value — logical constraint conflict may cause all rows to be flagged
• allowed_categories list exceeds 100 entries — rejected
• max_cell_length outside 1–5000 range — rejected
• Malformed CSV with unbalanced quotes — may cause parse errors or incorrect row boundaries