Engineering, Ops, On-Call Diagnose, re-run, and validate HCP OneLink contract sync issues Production & non-prod environments You have access to the CadenceFrontline server
This integration keeps in Cadence in sync with , using as the primary link.
- Cvent = event + roster + invite status
- HCP OneLink = contract status
- Cadence = unified Ensemble view
Contract updates are , not real-time. Use this table to jump to the right section.
Contract status didn’t update
Status shows “Not Connected”
One HCP blocking completion
Webhook fired but nothing changed
Integration appears stalled
- Integration runs
- If change was recent, data may not have synced yet
If needed, (Section 8) - Confirm the event exists in Cadence
- Confirm it is linked to Cvent:
"linked_event": {
"source": "cvent",
"event_id": "<CVENT_EVENT_ID>"
}
If missing → integration will not match
- Log into CadenceFrontline
- Locate logs
- Look for:
- Job start
- Errors
- Integration summary
If errors exist, resolve before re-running Confirm in OneLink UI:
- Event exists
- HCP contracts are present
- Contract status is correct
Cadence
- Primary email matches customer
- Secondary emails checked
- No duplicate customers with same email
Email mismatch is the #1 failure cause - Event does not exist in OneLink
- Integration not enabled
- Incorrect Cvent Event ID
Confirm event exists in OneLink
Verify correct Cvent Event ID
Manually re-run integration
- At least one HCP has incomplete contract
- MSA or RFS not completed
- Declined invitees (ignored)
- Identify HCP
- Resolve contract in OneLink
- Re-run integration
This is .
- Webhook = notification only
- No reconciliation occurs at webhook time
- Next scheduled job (or manual run) does the work
Manually trigger import if needed - Has the job run recently?
- Any rate-limit errors in logs?
- Was the server restarted?
- Is cron/scheduler active?
If unclear, manually run the job curl --location --request POST \
'https://webhookconnect.eventcadence.com/hcponelink/onelinkds360/cvent/import'
- No progress indicator
- Logs updated during execution
- Email on failure
- Summary logged on completion
Escalate if:
- Manual run fails repeatedly
- Logs show unhandled exceptions
- OneLink data is correct but Cadence remains wrong
Include in escalation:
- Cvent Event ID
- Timestamp of manual run
- Relevant log excerpts