Import Log
Every importer run is recorded on the Import Logs page in Flow. Depending on the amount of data, a run may take some time. Open the Import Logs page to review past runs of any importer.
Warnings indicate inconsistent data; the run still completes as SUCCESS. If only some entities fail (e.g. a datasource
returns malformed data or is unreachable) the run is recorded as PARTIAL; if the run cannot be completed at all it is
recorded as FAIL. Failures are recorded with the error message.
Import log
Each import run in the Import Logs list shows:
| field | description |
|---|---|
| Date | Date and time the import run started. |
| Duration | How long the run took. |
| Result | Overall result of the run: SUCCESS, PARTIAL (some entities failed) or FAIL. |
| Warnings | Number of warnings recorded during the run. |
| Errors | Number of errors recorded during the run. |
Details
Opening a run shows the change counts per imported entity together with all log messages:
| field | description |
|---|---|
| Entity | The imported entity (for example User, Organization, Course or Survey). |
| Inserted | Number of records that were newly inserted in this run. |
| Deleted | Number of records that were removed since the previous run. |
| Log messages | Individual INFO, WARNING and ERROR entries, each with a message and timestamp (errors also include a stack trace). |
Example log messages
A successful run may still record warnings, for example:
- WARNING — Could not import some events as the corresponding course is missing. Events that could not be imported:
<idOfEventWithMissingCourse>(Course:<idOfMissingCourse>) - WARNING — Some registrations reference a course that was not imported:
<courseId>
A failed run records the error that caused it, for example:
- ERROR — Could not fetch data from the datasource, please check the endpoint and its response format.