Run a manual sync

For: An admin or ops lead who needs fresher data right now instead of waiting for the next scheduled sync.

You’ll accomplish: knowing when a manual sync actually helps (and when it won’t), running one, and reading what happens during and after.

PropSocket syncs your PMS data on a schedule. A manual sync lets you say “go now” instead of waiting for the next scheduled run. It’s the same kind of sync — it just happens on demand.

You don’t need to write any code to run one.

---

1. When a manual sync helps

Run a manual sync when:

• You just made a change in your PMS and need it in PropSocket now — you added units, signed a lease, or fixed a record in Entrata and don’t want to wait for the next scheduled sync.
• You just enabled a property and want its data pulled in immediately (see Choose which properties to sync).
• You just fixed a connection problem — you re-entered credentials after a failure and want to confirm the next sync completes (see What to do when a sync fails).

2. When a manual sync won’t help

A manual sync is not a fix for everything. It won’t help when:

• The data is wrong in your PMS itself. A sync faithfully copies what’s in the PMS. If the source is wrong, syncing again just copies the wrong value. Fix it in the PMS first, then sync. See What if our data looks wrong?.
• The connection is broken. If credentials are expired or the PMS is unreachable, a manual sync fails the same way the scheduled one did. Fix the connection first.
• A sync is already running. PropSocket can’t run two syncs for the same integration at once. While a sync is in progress, the Sync Now button is disabled — let the current run finish, then trigger a manual sync if you still need one.
• You’re hammering it. Your PMS sets its own limits on how often PropSocket can ask for data. Triggering manual syncs back to back doesn’t get you data faster — it just queues behind those limits. One manual sync after a change is plenty.

3. Run it

1. Open the integration you want to refresh.
2. On the integration details page, choose Sync Now (it may open a short confirmation).
3. Confirm. The integration moves into a syncing state.

Both admins and members can trigger a manual sync.

4. What to expect during and after

• During: the integration shows syncing, and a new run appears in the sync history with status running. How long it takes depends on how much changed since the last sync — usually quick, since it only moves what’s new.
• After: the run reaches completed, and your last successful sync time updates. That’s your signal the data is current. See Reading the sync status dashboard for how to read these statuses.
• For your downstream systems: a manual sync behaves like any normal ongoing sync. If your team set up webhooks, only the records that actually changed fire notifications — a manual sync does not re-send your entire dataset or flood your webhook receivers. (That bulk behavior only ever happened on the very first sync.)
• If it fails: treat it exactly like any failed sync. Work through What to do when a sync fails.

---

If this didn’t work

If the Sync Now button is missing (and no sync is already running), the sync won’t start, or it starts but never completes, send us the details.

Open a support ticket by emailing support@propsocket.io and include:

• Organization slug (the short name in your dashboard URL, e.g. acme-residential)
• Integration Name (shown on the integration’s page)
• Sync job timestamp of the manual run, if one was created
• What you expected (e.g., “manual sync should complete and update last successful sync”)
• What you saw (the exact status or message)
• A screenshot of the sync history

You don’t need to send any data records or credentials — the IDs above are enough for us to find the run.