The job of this console
Pick the job, run or retry, verify the canonical row, watch health. Do not treat a successful job as a reason to skip product checks.
Integrations · Jobs
Import/Export Jobs
Connector batches — not Admin scheduled jobs, and not the payroll or timesheet UI itself.
Scroll to Flowcharts. Scenario: Run or retry a connector import/export job.
Batches
Connector jobs, not the admin cron board
Import/export jobs run connector batches. Admin → Scheduled jobs is platform cron. Humans still enter timesheets and payroll on those consoles.
Integrations → Import/export jobs
Route
/integrations/jobs
Org flag jobsEnabled
Integration admin · Ops
Seat at the table
Integration admins and ops with jobsEnabled.
The working rhythm
Schedule or run, watch, retry with a fixed map, verify.
Moments that bring you here
Nightly import. A failed payroll time export. After mapping change. Distinguishing this list from Admin jobs.
ⓘ
Wrong jobs console
If you needed leave accrual schedulers or other platform cron, that is Admin → Scheduled jobs.
Flowcharts
1 — Batch then verify
Run the connector job, open the entity it should have touched.
flowchart TD
A[Open Import/export jobs] --> B[Select job]
B --> C[Run / retry]
C --> D[Canonical register]
D --> E[Sync monitor]
- 1OpenIntegrations → Import/export jobs.
- 2JobBound to connection + map.
- 3RunOr retry failed.
- 4VerifyProduct row + health.
Overview
Import/export jobs are connector batches. Admin scheduled jobs is platform cron (including some leave schedulers). Timesheet and payroll UIs remain how humans enter those domains.
How to use
1. Idempotent imports
External id in the map.
2. Export scope
Do not dump the whole org for a vendor that needs one project.
3. Poison pill
Fix mapping before retry storms.