How to Sync Records (Anthology)

Element → Anthology#

Records can be synced from Element451 to Anthology either manually or automatically.

During UAT, we strongly recommend using manual syncs only. This helps prevent accidental syncing of any production data you might have loaded during onboarding.

---

Sync Timing

• A typical sync takes 12–15 minutes
• If a record does not appear in the Integration Log immediately, it may still be processing. Refresh the page every few minutes until it appears

---

Manually Syncing a Record#

1. In Element451, open the contact profile you want to sync
2. Add the label:
   • Element451 to CampusNexus - Trigger SyncThis will start the integration process.
     

     

3. Wait 10-15 minutes, then navigate to the Integration Log
   • For more details, see Reviewing the Integration Log below

Setting up Automatic Syncs#

1. In Element451, navigate to:
   • Data + Automations → Automations → Rules
     

   

2. Open the rule: Element451 → CampusNexus Sync
3. Under Triggers, add conditions to automatically start the sync. Common triggers include:
   • Application Submitted
   • Decision Released
4. Changes are saved automatically. You can exit once updates are complete.

---

Sync Behavior#

Once triggers are configured:

• The integration will run automatically when conditions are met
• Sync results can be monitored in the Integration Log

---

Anthology → Element#

Element uses a scheduled cadence to poll Anthology every x minutes, looking for records that were updated in that time frame since the last time it ran (this cadence is defined with the partner).

By default, it will only pull in new student records from Anthology and create them in Element. This can be further filtered to only look at records with specific school statuses. However, this process can also be configured to update existing Element records with changes if desired.

---

Reviewing the Integration Log#

The Integration Log is a critical tool for monitoring the status of integration activity.

It shows:

• Which records successfully synced
• Which records encountered errors
• Details needed to troubleshoot issues

We recommend reviewing the Integration Log at least daily to identify and resolve issues early.

---

Accessing the Integration Log#

1. In Element451, navigate to: Profile Picture (top right) → Settings → Integrations
   

   

2. Select Integration Log from the left-hand menu
   

   

3. The most recent sync records will appear at the top

---

How to Read the Integration Log#

Columns:

Each row represents a sync attempt. The columns include:

1. Name
   • The name of the student or record
2. Type
   • The direction and type of sync
3. Status
   • In Progress → Sync is currently running
   • Success → Sync completed with no errors
   • Error → One or more errors occurred
4. Processed At
   • Date and time the sync was processed
5. Error Summary
   • A brief description of the first error encountered
6. Error Details
   • Available via the ⋮ (ellipsis) menu
   • Select View to see:
     • Full error message
     • Payload and API details (if applicable)

---

Important

An Error status does not always mean the entire sync failed.

• Some parts of the record may have synced successfully
• Errors may be limited to specific components (e.g., application, previous school)

Review the Error Details to understand the full impact.

---

Integration Log Controls#

• Search (🔍)
  • Search records by student name
• Filter
  • Filter by:
    • Status (Success / Error)
    • Sync type/direction
    • Date range (Processed At)
      

      

• Paging
  • Navigate through multiple pages of results

Viewing Details of an Error#

When reviewing an error in the Integration Log, it is important to look at the full set of error details, not just the summary.

• A single sync can contain multiple errors
• Scroll through the error details to review all issues associated with that sync
• Some errors may not be critical, while others may block key parts of the process

---

Understanding the Error#

Most errors originate from Anthology.

Element451 typically provides:

• The error message returned by Anthology
• The API endpoint that was called
• The payload (data) sent during the request

Together, this information helps identify:

• What action was being attempted
• What data was sent
• Why the error occurred

---

Troubleshooting Steps#

1. Review the full error details in the Integration Log
2. If you are unable to resolve the issue, contact Element451’s Live Support: How to Work with Live Support (Managed Integrations)

Note

• Some errors may be specific to your SIS configuration
• Because Anthology is not managed by Element451, you may be directed to open a ticket with Anthology support

---

Re-Syncing a Record#

Once the issue has been resolved:

• Open the contact profile in Element451
• Add the label: Element451 to CampusNexus - Trigger Sync

This will re-run the integration for that record.