What Current writes back to Syncro (and when)
Reading from Syncro is always on once you connect. Writing is the part with gates, and this page is the full list: what has to be open, what sets a write off, and what Current will not write at all.
The gates, in order
- 1The project has to be a Syncro projectA Current-native project never calls Syncro, whatever else is switched on. Current is the source of truth for those, and the check happens before anything else.
- 2Two-way sync has to be onThe switch in the Syncro card's Manage drawer. It is on by default and covers task and project writes. Off means Current pulls and never pushes.
- 3CRM write mode decides CRM writesOff by default. Test mode only writes to companies whose name starts with ZZ-Current Test, so you can prove the path on records nobody bills. Live mode writes to real customers.
- 4The person has to be allowedProject and task writes need a project manager or above. An account executive can push their own book's companies, contacts and deals, checked against their ownership in the database rather than in the interface.
- 5The token has to carry the permissionA missing Edit permission comes back as a named refusal rather than a silent no-op.
What triggers a push, by entity
| You do this in Current | Current writes this to Syncro |
|---|---|
| Deploy a project to your PSA | A parent ticket, plus a child ticket for each task |
| Rename a task, move its dates, change its status or assignee | The matching child ticket's subject, start date, due date, status or assignee |
| Change a project's name or end date | The parent ticket's subject and due date |
| Log time on a project task or a ticket | A ticket timer entry against a Labor product |
| Comment on a synced ticket | A ticket comment. A co-managed comment is posted; an internal one is held back until Current has confirmed Syncro keeps it private |
| Create or edit a company or contact in your book | A customer or contact, when CRM write mode is on |
| Move a deal's stage, or win or lose it | The Lead's status, through your stage map |
| Convert a won quote | Charges on the parent ticket, and the estimate set to Approved |
Read, merge, write, and why Current never blind-retries
Some Syncro updates replace the whole record rather than only the fields you sent. So every update reads the record first, changes only the fields it means to change, sends the whole thing back, and reads it again to confirm Syncro stored what it was given. If Syncro kept a different value, that becomes a visible conflict on the record rather than a second write that fights with your team.
When a write fails without a clear answer, a timeout or a server error, Current does not retry it on its own. A retried create is a duplicate: a second parent ticket, a second customer, or a second timer entry billing the same hour twice. Instead the row is left in a state you can see, with the reason on it, and a person decides.
Time entries, billing and invoiced time
- ＋Before creating a timer entry, Current looks for one it may have already created for that entry and adopts it instead of adding another.
- ＋Time needs a Labor product. Without one the entry stays in Current with the reason on it, rather than being sent to bill against the wrong thing.
- ＋Once Syncro marks an entry invoiced it is immutable. Current marks it approved and posted and stops writing to it. Edits belong in Syncro from that point.
- ＋A billability change that fails after the time itself landed is recorded as exactly that, a billability that did not stick, and the time is never sent again.
Syncro allows 180 calls a minute per address, and that budget is shared by every workspace Current syncs with Syncro. Current works to a fair share of it. A run that reaches the limit stops and picks up on the next one, and reports that rather than an error, so a first sync of a large account is slower than the same account on another PSA. Pushes you make are small and go out as they happen; the long walks are what wait.
What a push can never touch
- ＋Company notes. Syncro has one free-text field on the customer and no note log, so Current keeps notes on its own side rather than rewriting a field your team owns.
- ＋Company attachments, phases and task dependencies. Syncro has none of them.
- ＋A customer's estimate decision. Current can set an estimate Approved when someone converts a won quote, and never sets one Declined.
- ＋Cost, invoices and rates. Money is Syncro's.
- ＋Anything on a customer's machine. Asset and RMM data is read-only, and Current never schedules a script or mutes an alert.