Integration logs

Integration Logs records tenant integration activity and helps connect a bridge run to staged or operational records.

Investigate a problem

1. Note the environment, tenant, job type, run time, and affected source identifier.
2. Filter the log to the smallest matching time range and domain.
3. Read the status and validation/error details.
4. Compare the event with the corresponding SR-Bridge local log.
5. Correct the source record, mapping, authentication, or parent-data issue.
6. Retry only the failed scope and verify the new result.

Common causes include expired or incorrect API credentials, wrong environment, missing required fields, an unknown parent job/phase/code, mapping differences, duplicate source identifiers, and local database connectivity.

When requesting support, include timestamps, job/domain, source IDs, status, and sanitized error text. Exclude API keys, tokens, passwords, personal data, and database credentials.