Skip to main content
The Jobs page lists all sync and replication jobs for the Organization. Each row shows the job type, domain, status, when it was created, and what it changed.

​
What a job changed

The Changes column summarizes what the job wrote. For a replication job, that is what it wrote to the target system: the sections it touched and the fields it changed, for example “Salaries +1, Bank account nr”. For an employee sync job, it is what the sync changed in Twine: the properties it changed, and the job’s page adds how many employees each one changed for. It shows names only. The values themselves are only in the job’s log.
  • No changes means the job compared the employees with the other side and found nothing to write.
  • Not recorded means Twine cannot say whether the job changed anything. Jobs that ran before this was introduced (September 2026) read this way. So do syncs of anything but employees, replication to the few systems that cannot compare, such as file exports, and jobs that wrote parts Twine does not record yet when none of the parts it does record changed: some systems’ replicated salary or employment history, or the work schedules a Hibob sync brings in. It does not mean nothing changed.
  • A dash means the job has not finished yet, or was skipped.
Two filters build on this:
  • Changes narrows the list to jobs that changed something, changed nothing, had changes held back (for example by a merge conflict), or did not record.
  • Changed fields finds the jobs that changed any of the fields you name. You can use a Twine property name (salary_amount), a field name in the target system, or a section name (salaries), separated by commas.
Combined with the IDs filter, this answers “which jobs changed this employee’s salary” directly.

​
Job details

Clicking a job opens its detail view. This page shows the job’s metadata, its current status, any descendant jobs (for example, the replication jobs spawned by a sync), and a streaming log of everything that happened during execution. The log is the primary surface for understanding what a job did and why it failed. A job’s log and its data are removed three months after the job ran. The job itself stays for 13 months, with its status, timing, Changes and Run, so older jobs can still be found and filtered, but they can no longer be requeued. The Changes card on the detail page lists what the job changed: each section with how many records were created, updated, deleted and kept, and the date the earliest change takes effect from, the Twine properties and target-system fields it wrote (inside a section too: a new salary names its amount and period), and anything it computed but held back, such as a section with a merge conflict. For an employee sync, it lists each Twine property with the number of employees it changed on and the earliest date the change takes effect from, and how many employees were created, updated or deactivated. Below it, Run shows how the job started (by its schedule, by someone in Twine, through the Public API, by a webhook or an SFTP upload, or as a requeue of another job), the software version that ran the job, a configuration fingerprint, and how many requests the job made to the system, with how many of them failed. Two jobs with the same fingerprint ran with the same mappings and settings. A different fingerprint usually means someone edited the configuration between them; it can also change once when a Twine update changes how an integration’s settings are stored, in which case the software version changes at the same job.

​
Terminating a running job

The detail page for a running job displays a terminate button. This kills the underlying process immediately rather than waiting for it to finish gracefully.
Termination is forceful - it stops the process without giving it a chance to complete its current step. While most operations run inside database transactions (so partial writes are rolled back), there is a small risk of inconsistent data if the job was mid-way through a non-transactional operation. Use this only when a job is stuck or needs to be stopped urgently.