How do I monitor a TempWorks sync?

Last updated: May 28, 2026

The TempWorks sync records page shows the status of every entity Onboarded has tried to sync from TempWorks. Use it to confirm data landed correctly and to diagnose failed records.

Where to find it

Navigate to Integrations → TempWorks. The records table is on this page, below the sync status summary.

Reading the sync status summary

At the top of the page, a status banner shows the state of the most recent sync for each entity type. Possible states:

  • In progress — the sync is still running. Record counts shown so far are partial.

  • Completed — the sync finished successfully.

  • Failed — the sync encountered an error partway through. Records that processed before the failure are retained; the count shown reflects what synced before it stopped.

  • Cancelled — a new sync was started before this one finished. Records processed before cancellation are retained.

The status indicator beside the sync button also gives a quick read: an amber pulsing dot means syncing is in progress, green means up to date, red means the last sync failed.

Reading the records table

Each row in the table represents one synced entity. The columns are:

  • TempWorks Entity Type — the type of record from TempWorks: Employee, Job Order, Customer, Assignment, Employer, or Onboarding Action.

  • TempWorks Entity ID — the ID of that record in TempWorks. Copyable.

  • Onboarded Entity Type / ID — the corresponding record in Onboarded. Click View details to open it directly.

  • StatusSuccess (green) or Failed (red).

  • Last Synced At — when the record was last processed.

  • Error Message — for failed records, shows what went wrong. Format: Failed at {field}; {value}, or Created {type}; Failed at {field}; {value} if the Onboarded record was partially created before the failure.

Filtering records

Use the filters above the table to narrow down what you're looking at:

  • TempWorks Entity Type — filter to one entity type (e.g., show only failed employees).

  • Status — filter to Success or Failed.

  • TempWorks Entity ID — look up a specific TempWorks record by its ID.

  • Onboarded Entity ID — look up which TempWorks record corresponds to a specific Onboarded entity.

Re-running a sync

To pull fresh data from TempWorks, go to Account Settings → Integrations, click Configure next to TempWorks, and advance to the Sync Records step. Click Sync again (or Restart sync if one is in progress).

Restarting cancels the current sync
Starting a new sync immediately cancels any sync that's currently running. Records processed up to that point are kept. Sync time depends on the size of the account.

After the initial sync, Onboarded stays up to date in real time via webhooks — TempWorks pushes changes as they happen (new employees, job order updates, assignment changes, etc.). You only need to manually re-sync if you're troubleshooting missing records or after a configuration change.

Understanding Onboarding Action records

Onboarding Actions are the one entity type that flows from Onboarded to TempWorks rather than the other way around. Each row represents an Onboarded task that was pushed to TempWorks. A failed Onboarding Action record means the task didn't land in TempWorks — check the error message for the field that caused it.

Troubleshooting failed records

Error: "Failed at {field}; {value}" — A field mapping failed during sync. The field name and the rejected value are shown. Common causes: wrong scalar type in your field mapping, an address with an unrecognized country code, or an address missing required fields. Fix the mapping in the Configuration step, then re-run the sync.

Error: "Created {type}; Failed at {field}; {value}" — The Onboarded record was created but one field couldn't be populated. The record exists in Onboarded but is incomplete. Fix the mapping and re-sync to fill in the missing field.

Many records showing Failed after a sync restart. If you changed field mappings and then re-synced, records that were previously mapped to a now-removed path may show as failed until they re-sync with the updated mappings.

Related