Error handling for laboratories

This section explains common problems and errors and how to deal with it.

Errors and warnings

The Connect API might return a response containing and error or warning object. If you receive an error the execution of the call is stopped and no further actions are being perfomed by the system. Please check your received errors, fix them, and execute the API call again. Most errors have a code and a message that explain the source of the issue.

Warning are being returned in case of non-critical errors. For example, it´s possible to create a test-pool with not checked-in tests. However, in order to submit a result, the test has to be checked-in.

Test Check-In missing

Sometimes it happens that tests are not checked-in. This can be due to a technical or personal issue in the testing facility. When using the Connect API you should know how to deal with such issues.

There are two different behaviours for not checked-in tests, depending of the use-case.

Pool tests

It´s possible to create test-pools with not checked-in tests. In this case, a warning is returned by the API and you should try to get this sorted (by contacting our support or the testing facility). If the test can be checked-in until the test is evalulated, no further steps have to be taken.

If the test is not checked-in 'till you enter the result of a pool, not checked-in tests will be ignored (as entering a result for a not checked-in test is currently not possible). In this case the testing facility is notified automatically about the issue and has to resolve the issue. All other tests in the pool - that have been successfully checked-in - receive their result immediately.

Single tests

In case of normal / single tests, the API throws an error in case of not checked-in tests. The testing facility is notified automatically and has to resolve the problem. Please note: they might come back to you in order to submit the result again after they checked-in the test.