Skip Invalid xAPI Statements with Inbound LRS Data Error Logging

Watershed's newest feature ensures that the connection between separate Learning Record Stores (LRSs) is maintained when data sources deliver bad statements.

What's Inbound LRS Data Error Logging in Watershed?

All xAPI-conformant LRSs are required to validate incoming learning data. This means data sent to Watershed from another LRS should be valid.

However, if an LRS sent invalid data to Watershed in the past, Watershed would generate an error message and stop receiving statements until the error was fixed. Otherwise, neglecting to validate statements would have resulted in reports with bad data and misleading information.

With Inbound LRS Data Error Logging, Watershed skips invalid statements sent from other LRSs while continuing to accept good statements. Now, bad xAPI statements are skipped and can be found in a statement log (see below).

How do I import statements from another LRS into Watershed?

For more information on Inbound LRS Data Error Logging, read our help section article.

Subscribe to our blog

Ready to get started?

To learn more about using all of Watershed's features, visit our help section. You're also welcome to contact us if you have any questions or would like to request a demo.

This website stores cookies on your computer to improve your experience and the services we provide. To learn more, see our Privacy Policy