Turn on offline sync for a project

Before the field app can send work into a project, the project needs a starting point: the network as it is now, stored once. Every change after that arrives as an op and is replayed from that starting point (Offline sync).

Before you start

• The project exists, with its network and any OTDR traces already ingested; they become part of the starting point.
• Its history is consistent: every span that was retired before sync must have been retired by a recorded split.
• DATABASE_URL is set.

Steps

1. Turn sync on:

   $ asbuilt sync enable --project <project>
   …
   

2. Running it again changes nothing. From now on, change the project only through ops: from the field app, or as office ops through the same path.

Check

asbuilt sync pending runs without error for the project (Watch for waiting work), and ops pushed by the field app reach APPLIED.

What can go wrong

You see	Meaning	Do
retired span … has no lineage entry	A span was retired outside a recorded split, so a replay could not reproduce the network.	The project cannot be enabled as it is. Report it: its history has to be corrected first.
no such project	The name or id is wrong.	Check the project’s name.