Skip to main content

error-0266

Associated Prime Contract is not Synced

In the Errors tab, you might see an error message related to a Change Order, typically shown as:

error
  • Associated Prime Contract is not synced: CO #1

Causes​

This error occurs when the related Prime Contract hasn't been synced between systems. Common reasons include: the Prime Contract was never pushed or linked, or the destination system doesn't recognize or support the format of the Prime Contract.

How to fix it​

To fix this problem, follow these steps:

  1. Identify the record(s) you're trying to sync and note the associated Prime Contract.
  2. In Agave, navigate to the Prime Contract module via the side panel:
    • Global → Prime Contract
  3. Search for the relevant Prime Contract(s), then select and push them to Procore.
    • If the Prime Contract(s) already exist in Procore, you may have the option to autolink them.
  4. Once the Prime Contract(s) are pushed or autolinked, retry the sync.

Still having trouble?​

Contact Agave Support for help