Skip to main content

Run and Verify Your First Sync

Once you've connected a source and mapped your fields, Oho is ready to bring your people in. This guide covers how to kick off that first run, confirm it worked, and understand what you're looking at if something looks off.

What you'll end up with

Your people visible in Oho under All Workers or All Applicants, with credentials queued for verification — and a clear picture of the run's health from the first result.

Starting the sync​

Every connection has two run modes: once and recurring.

  • Once — runs immediately when you save. Use this to test a new connection before committing to a schedule. After it runs, check the result and decide whether to set a recurring schedule.
  • Recurring — Oho re-reads the source on your chosen cadence (hourly, daily, weekly, or a custom schedule). Changes in the source flow through automatically on each run with nothing to re-enter.

You can also trigger an on-demand run at any point while a recurring schedule is active. On the connection's detail page, click Run now.

Checking the result​

After a run completes, the connection shows a status on the Data Sources page:

StatusWhat it means
CompletedAll records processed cleanly
Completed with warningsSome records were processed, but others were skipped — the run log explains why
FailedThe run did not complete; no records were imported
In progressCurrently running

Open the run log (click the connection name, then the timestamp of the most recent run) to see what happened at the per-record level.

Per-record outcomes​

Each record in the run log shows one of three outcomes:

OutcomeWhat it means
✅ ImportedRecord created or updated successfully
⚠️ SkippedRecord was found but not imported — a reason is shown alongside it
❌ ErrorRecord caused a processing error — the error message is shown

Where your people appear​

  • Workers — go to All Workers in the left menu. Newly synced workers appear at the top when sorted by Date added.
  • Applicants — go to All Applicants. Filter by Source and select your connection name to show only records from this connection.

Allow up to 60 seconds after a run completes for records to appear in search results.

What a healthy first run looks like​

A clean first run shows:

  • Status: Completed with no warnings
  • Imported count close to your expected number of records
  • No errors in the run log
  • Workers or applicants visible in Oho with correct names and mapped fields

A note on counts: if your source file contains a header row, a totals row, or blank rows between records, the imported count will be lower than the raw row count — those non-data rows are skipped automatically and don't show as errors. A small number of skipped records (under 5%) alongside all others importing cleanly is still a healthy result, provided the skip reasons are explainable.

Troubleshooting​

Nothing imported​

Likely causeWhat to check
Auth credentials are invalidRe-enter the credentials in the connection's settings and re-run. For OAuth connections, disconnect and reconnect the integration.
Source is emptyOpen the source and confirm it contains records in the expected location (sheet, folder, or table).
Oho can't read the file or folderFor shared files, confirm the share link or service account has read access to the specific file — not just the parent folder.

Some records skipped​

Skip reasonWhat it meansFix
Heading mismatchA column header in the source doesn't match what Oho expectsOpen the source file and check every column header against the field mapping reference. Headers are case-sensitive and must be spelled exactly as the template shows.
Credential row not matched to a workerA credential row references a worker who wasn't foundMake sure the Work Email on the Credentials sheet matches the Work Email on the Workers sheet exactly. If importing workers and credentials together, both sheets must be present and consistent in the same run.
Required field missingA required field (usually Work Email) is blank for that rowFill in the missing field in the source and re-run.

Auth stopped working after previously running fine​

OAuth tokens and API keys can expire or be revoked when a password changes, access is removed, or the authorising account is deactivated.

  • OAuth — open the connection's settings and click Reconnect. This re-runs the OAuth flow and issues a fresh token. Takes about 30 seconds.
  • API key — paste the new key under the connection's Settings → API key and save.

Duplicate records appearing​

Check Data Sources for multiple connections pointing to the same source and remove any extras. For file imports, duplicates usually mean the match key (Work Email) is missing or inconsistent — rows without a match key always create a new record instead of updating an existing one. See Map your fields → Recognising the same person again.

Source unreachable (SFTP)​

SFTP hosts must be publicly reachable from Oho's network — a host behind a corporate VPN or firewall will fail with a "source unreachable" error. Ask your IT team to add Oho's outbound IP addresses to the SFTP server's allowlist. You'll find Oho's IP addresses under Settings → Security → IP allowlist.

When to contact support​

If you've worked through the steps above and the issue persists after one retry, contact support with:

  • Connection name — as it appears on the Data Sources page
  • Run time — the date and time the failing run started (shown in the run log header)
  • Request ID — shown in the run log under Run details → Request ID (format: req_xxxxxxxxxxxx)
  • What you've already tried
  • A screenshot of the run log if the failure is at the record level (skipped or error rows)

Reach support via the in-app chat (bottom-right corner) or at support@weareoho.com. Include "URGENT" in the subject line for production-blocking issues.