Integration troubleshooting checklist
Use this before contacting KORONA Event support about failed imports, exports, membership lookups, POS sync, or entry-system problems.
Start with the integration page
Open Admin > Integrations.
Check whether the relevant integration is enabled, whether credential fields are present, and whether the page shows external system calls or connection status.
Gather evidence
| Evidence | Example |
|---|---|
| Affected system | KORONA.studio, KORONA.entry, bLoyal, or another connected system. |
| Direction | Import to KORONA Event, export from KORONA Event, scan validation, or membership lookup. |
| Identifier | Order number, invoice number, receipt number, ticket number, customer email, or external ID. |
| Time | When the action was attempted, including timezone. |
| Recent change | Password rotation, domain change, POS change, event edit, or provider outage. |
| Error | Exact message, screenshot, or external system status. |
Safe credential check
Use Edit credentials only when an authorized admin must update credentials. Do not expose passwords or secret keys in screenshots, tickets, chat, or email.
Confirm whether credentials were recently changed and whether the external system also needs the change.
Expected result
You can identify whether the issue is configuration, credentials, external system availability, data mismatch, or a KORONA Event workflow problem.
Troubleshooting
| Problem | What to check |
|---|---|
| External ticket does not scan | Integration enabled state, ticket number, event date, customer identity, and external system status. |
| Customer benefit not applied | Customer email, duplicate customer records, external ID, and membership sync. |
| Credentials were changed | Update both systems where required and retest one known record. |
