job_…) represents a single transactional run of a file or set of files through a validation, preflight, or optimization pipeline.
Jobs are generated automatically when customer uploads flow through a storefront Workflow, but they can also be initiated manually by administrators for instant preflight or optimization (saving you from running a workflow “ritual”).
As a job progresses, it emits interactive, real-time status events.
Job statuses
Filecheck tracks the lifecycle of every file through standard statuses:“Manual review” uploads. When a Rule’s onFail policy is Manual review, the file is accepted but held for an admin to approve before it proceeds.TODO(filecheck): document the status value a held-for-review file reports, whether
canProceed is false while held, and how it clears once an admin approves.Gating with canProceed
To protect your checkout pipeline, Filecheck exposes a simplecanProceed boolean alongside the job status.
canProceedistrueonly when the job is in areadyorpartialstatus.- When
canProceedisfalse, your e-commerce plugin or custom submit button remains disabled.
Persisting and retrieving job output
WhencanProceed is true, the browser receives a finalized jobId.
- At Checkout: The
jobIdis passed and stored as meta-data on the customer’s order. - Post-Purchase Fulfillment: The validated, fixed, or optimized production files can be retrieved in two ways:
- E-commerce Dashboard: Attached directly to the WooCommerce, Shopify, OpenCart, or PrestaShop order page for immediate download.
- Filecheck Portal: Searched and downloaded under the Jobs tab at admin.filecheck.io/jobs.
- REST API: Downloaded programmatically via
GET /jobs/{id}using your secret key. See Verify jobs.