Summary
Integration Logs and Status let you review the run history of an account's integrations and see the state of each integration job. Every job carries a status (waiting, in process, succeeded, failed, canceled, or locked) along with its log and attempts, and an audit record captures configuration changes. This article explains how to read these logs and interpret each status.
Introduction
KnowledgeCity integrations move real data, including users, enrollments, and results, between the platform and connected external systems. Each integration action runs as a background job, and the Logs view is where you watch those jobs run and confirm they finished as expected.
This view is used mainly by Customer Support and Operations. When a sync stalls, fails, or produces unexpected results, the logs and statuses are the first place to look to understand what happened and why.
Key Concepts
- Job: a single integration task (for example, a user import) that runs in the background, each with its own status and log.
- Status: the current state of a job, such as waiting, in process, succeeded, failed, canceled, or locked.
- Log: the per-job record of what the job did, used to investigate why a job behaved the way it did.
- Attempts: how many times a job has been tried, which helps you spot jobs that are repeatedly retrying or stuck.
- Handler: the process that runs a job, identifying which kind of integration work was performed.
- Audit record: a history of integration configuration changes for the account, useful for confirming who changed what and when.
Steps to Follow
Opening the Logs view
Navigate to the integration for the account you are investigating and open its Logs tab. This view lists the integration's jobs along with the status and log for each run, so you can review the account's integration run history in one place.
Reading a job's status
Each job shows a Status that tells you where it is in its lifecycle. Interpret the states as follows:
- waiting: the job is queued and has not started running yet.
- in process: the job is currently running.
- succeeded: the job completed successfully.
- failed: the job did not complete; open its log to find the cause.
- canceled: the job was stopped before completing.
- locked: the job is held and not eligible to run at the moment.
Inspecting logs and attempts
When a job did not finish as expected, open its Log to see the details of the run, and check the Attempts to see how many times it has been tried. A rising attempt count on a failed or locked job is a strong signal that a sync needs attention.
Reviewing the audit record
Alongside run history, use the integration's Audit Log to review configuration changes for the account. This is helpful when a sync starts behaving differently and you need to confirm whether a setting was recently changed, and by whom.
Note: Integration jobs sync real user and course data with external systems. Always review a job's log and confirm the cause before re-running or changing the status of a sync.
Conclusion
The Logs and Status view is the operational window into an account's integrations: it shows every job's state, log, and attempts, and pairs run history with an audit record of configuration changes. Reading these statuses and logs is the fastest way to confirm a sync succeeded, or to diagnose one that did not.