Learn about the warnings and errors you may encounter when importing a dataset to Labelbox.
State | Description |
---|---|
Processing | A data row ingested is initially in the processing state. The data row will remain in the processing state until it is fully processed. |
Success | The processing of a data row will either succeed or fail. A success state indicates that the data row processing was successful. If the data row processing was successful, the data row shows up in your Catalog dataset. The data row can now be used to achieve any workflow in Labelbox. |
Failure | The processing of a data row will either succeed or fail. A failure status indicates that the data row processing has failed. If the processing of the data row fails, the data row will have a processing issue. It could be an error or a warning. Processing issues help you identify problems with your ingested data early on. Data rows with issues will be caught during ingestion, rather than later in downstream workflows. For example, a data row with a processing issue, will not appear in the Catalog. Hence, it cannot be sent to labeling from the user interface. |
This dataset has some data rows that are being processed
4794 data rows are being processed in this dataset
Click this icon to access the processing issues view
The processing issues view shows all data rows with processing errors and warnings
Ways to filter data rows on specific errors or warnings
You can reprocess data rows from the processing issues view.
Name | Description | Severity | User remediation |
---|---|---|---|
InternalError | An internal error prevented the data row from being processed. | Error | Reprocessing may or may not fix the issue. If the issue persists after reprocessing, contact support. |
FetchFailed | The data row could not be fetched. | Error | Check that the data row URL is correct and that the Labelbox backend has access to the data row URL. If using Delegated Access, verify that it is set up correctly. Then try reprocessing. |
FetchTimeout | The data row could not be fetched due to a timeout error. | Error | Check that the data row URL is correct and that the server is responding to requests for the data row URL in a timely manner. Then try reprocessing. |
Forbidden | The data row could not be fetched because access was forbidden. | Error | Check that the data row URL is correct and that the Labelbox backend has access to the data row URL. Then try reprocessing. |
NotFound | The data row could not be fetched because it was not found. | Error | Check that the data row URL is correct and that the Labelbox backend has access to the data row URL. Then try reprocessing. |
TooManyRequests | The data row could not be fetched due to a rate-limiting error. | Error | |
InvalidCors | The data row is being served with invalid CORS headers. This will result in a degraded labeling experience. | Error for text data rows | Check that the data row URL is being served with the correct CORS headers. See Configure CORS to learn more. Then try reprocessing. |
ConversionFailed | The data row failed to be converted from its original format to a new format required for labeling. | Error | The geospatial file may not be compatible with Labelbox. Check the supported geospatial file types and requirements. Try reprocessing. Contact support if the problem persists. |
InvalidEspg | The data row has invalid ESPG metadata. | Error | Review Labelbox’s ESPG requirements (do we have any?), fix the ESPG metadata, and reupload. |
TooManyBands | The geospatial data row has too many bands. | Error | Reduce the number of bands in the geospatial file and reupload. |
Number of processing errors
Name | Description | Severity | User remediation |
---|---|---|---|
InvalidCors | The data row is being served with invalid CORS headers. This will result in a degraded labeling experience. | Warning for non-text data rows | Check that the data row URL is being served with correct CORS headers. Then try reprocessing. |
Number of processing warnings