Document 27 request examples for existing Workday inputs and safe full-snapshot comparisons.
Reuse one terminating HTTP worker for concurrent batches after native repeated-worker import stalls; preserve per-request deadlines, fresh proxy sessions and identity-correlated replies.
Live Workday jobs from both public URL families, company and careers-page discovery, CSV/XLSX/Google Sheet intake, source facets and filters, full descriptions and published pay. Count-checked pagination and facet partitions protect snapshot comparisons. Optional change feed reports new, changed and closed roles; incomplete collections never infer closures. Request errors are separate from dataset rows, and maximum-charge responses stop further work.
Snapshots mark baseline eligibility explicitly. Relative posting-age and deadline labels do not create paid changes. Source deadlines terminate blocked DNS and reads; valid rows survive malformed-page neighbors. Dataset write failures are reported separately, and full-description snapshots stream delivered rows.
Default alternate-family detail requests start on datacenter and use fresh residential retries after a measured transport failure. Explicit proxy inputs retain their chosen egress.
-
Retain source-listed unavailable-detail facts with detailUnavailable, null unknown fields and ERRORS reasons; continue later partitions after a leaf failure without permitting incomplete snapshot changes.
-
Prefer count-covering partitions requiring fewer twenty-job list pages; retain all union and source-count checks.
-
Use the array JSON editor so Apify accepts both documented URL strings and url objects before Actor execution.