Appearance
LGL Sync
Little Green Light (LGL) is Upstate International’s CRM — the source of truth for constituent and gift data. UIEngine syncs information from UIEngine to LGL so that new members, memberships, payments, and enrollments appear in LGL without staff re-entering anything. This page explains what gets synced, when sync runs, how to check status, and when to retry or ask for help.
Used by: Admin.
What Little Green Light Is and Why It Matters
LGL is the organization’s constituent and donation database. Donor records, gift history, and campaign data live there. UIEngine does not replace LGL; it feeds LGL with data from the website (memberships, payments, class enrollments). Keeping sync healthy means LGL stays up to date for reporting, appeals, and stewardship.
What UIEngine Syncs To LGL
UIEngine sends the following to LGL:
- People (constituents) — New users and updated profiles so LGL has the right names, emails, and contact info.
- Memberships — Membership tier, status, and dates.
- Payments as gifts — Membership payments, class and event payments, and other revenue recorded as gifts in LGL.
- Class and event enrollments — Who is enrolled in which class or event.
- Family relationships — Links between primary members and family members where applicable.
Sync is one-way: UIEngine → LGL only. UIEngine does not pull data back from LGL. Changes made in LGL are not written back into UIEngine.
When Sync Happens
Sync runs automatically in the background. After any membership purchase, payment, or enrollment change (and other relevant actions), UIEngine adds a sync job to a queue. A background process runs about every 30 seconds, picks up pending jobs, and sends them to LGL one at a time to stay within LGL’s limits. You do not need to run sync manually for normal operations.
How to Check Sync Status
- Go to https://ui-admin.fly.dev/admin/sync.
- The queue shows sync jobs in one of these states: pending, running, or failed.
- Each job is labeled with what it’s syncing (e.g. user, membership, payment, enrollment).
- Use filters (if available) to show only failed jobs when you’re troubleshooting.
This page is your main view for “is sync working?” and “did this specific thing make it to LGL?”
Sync vs System Pages
| Page | Path | Purpose |
|---|---|---|
| Sync | /admin/sync | Job list and sync actions. View the queue, see pending/running/failed jobs, and retry failed jobs. Use this when you need to see or fix individual sync jobs. |
| System | /admin/system (and LGL under /admin/system/lgl) | System health overview. Connection status for LGL (and other integrations), sync queue summary counts, database counts, and quick links to LGL hub, queue, and audit logs. Use this for an at-a-glance health check. |
How to Retry a Failed Sync Job
- Go to https://ui-admin.fly.dev/admin/sync.
- Find the failed job in the list (filter by “failed” if the UI allows).
- Open the job or use the Retry action for that job.
- The system will try to send that item to LGL again. If it succeeds, the job will clear from the failed list.
INFO
Sync failures do not affect UIEngine itself. The member’s account, membership, and enrollment are fine. Only LGL may be out of date until the job is retried or fixed.
When to Retry Yourself vs When to Call Andrew
- Retry yourself: A single failed job with no pattern (e.g. one-off network glitch). Use Retry and see if it succeeds.
- Call Andrew: Many failed jobs at once, or the same job keeps failing after retry. That can indicate an LGL API issue, configuration problem, or data that LGL is rejecting. Do not change LGL API settings yourself.
WARNING
Do not change LGL API settings in /admin/settings/lgl unless directed by Andrew. Incorrect settings will break all syncing.
Summary
- What: People, memberships, payments (as gifts), enrollments, and family relationships sync from UIEngine to LGL. Sync is one-way only.
- When: Automatically, about every 30 seconds, after purchases, payments, and enrollment changes.
- Where to look: https://ui-admin.fly.dev/admin/sync for the job queue; https://ui-admin.fly.dev/admin/system for overall health and LGL connection status.
- Failed jobs: Retry single failures yourself; contact Andrew if many fail or the same job keeps failing. Do not change LGL settings without his direction.
Need help? Contact Andrew.