Errors
This guide outlines errors that you might see when creating, modifying, or deleting tileset sources, tilesets, and tileset recipes using Mapbox Tiling Service (MTS).
Job failures
If a tileset publish job fails, you can find information about any errors by querying the Retrieve information about a single tileset job endpoint.
| Error | Troubleshooting |
|---|---|
| Expression errors | An expression in your recipe could not be evaluated, which caused the tileset job to fail. This error will include the zoom level, layer and type of error to help you troubleshoot. As an example, [expression] less than operator can not compare values of type 'null' and 'number' - Example: tile z: 0 x: 0 y: 0, layer_name: trees indicates that some features in your source data were missing a numerical property which was necessary to evaluate your recipe. To fix, you would either update the recipe to no longer rely on the numerical property, or update your source data to include the numerical property on every feature, and then re-publish your job. For more information, see our recipe reference. |
| No features in source data. | If the size of your tileset source(s) referenced in your recipe is 0, there is nothing for MTS to process. Post data to the source and re-publish to populate your tileset with GeoJSON. |
| No GeoJSON features processed. Make sure your GeoJSON is line-delimited. | MTS requires that you format tileset sources as line-delimited GeoJSON. If you upload your source as GeoJSON using the tilesets CLI, your source will be converted to the correct format. Otherwise, see our docs for help converting your data into line-delimited GeoJSON. |
| No tiles were created because the recipe removed every feature. You may need to change the filter or limit configurations. | If your recipe limits or filters out all the features in the tileset source, there is nothing for MTS to process. Update your recipe with a smaller limit, or more permissive filter, and re-publish your tileset. |
| Unable to read tileset source data. Do not delete sources before tiling jobs complete. | Make sure you don't delete a tileset source that is being used by a tileset with any processing jobs. Post data to the source and re-publish to populate your tileset with GeoJSON. |
| Job exceeded max allocated time | If a job does not succeed within a reasonable amount of time, it is killed. Different sizes of jobs have different timeouts: the error message will say the size tier of your job, and the timeout for that size tier. If this is a persistent error, reach out to support for more help troubleshooting. For Raster Jobs, you can try to split large files into smaller chunks and add them as separate sources. A single source can have 10 files, but there can be as many source as you need. |
| Error processing tileset :tileset_id, job :job_id. Contact support. | A common reason that a tileset publish job might fail is that the tileset contains too much data at too high of a max zoom. If your data does not need the level of precision offered by a higher max zoom, we recommend using a lower max zoom level, which may cause a failing job to succeed. Learn more about which maxzoom level to use based on your data and use case. Reach out to support for more help resolving this error. |
| Invalid recipe | If a recipe is published that does not follow recipe specification, MTS endpoint will return error 401, and the cause of it. To resolve this, make sure the submitted recipe follows the specification. |
| Unable to continue tiling large job. Consider using a smaller maxzoom in the recipe. | The recipe provided is attempting to tile an area that would generate too many tiles relative to the source bounds. Using a smaller maxzoom value in the recipe can drastically reduce the number of tiles generated. |
If a publish job fails, I want to retry it automatically
If a tileset publish job fails, you may be interested in retrying it automatically. To do this, set up your system so that it queries the Retrieve information about a single tileset job endpoint on a set interval. If the response object indicates stage: failed, your system should re-publish that tileset.
Tilesets CLI errors
The following is a list of common errors that you may see when using the Tilesets CLI, which allows you to interact with and prepare data for Mapbox Tiling Service.
No features in source data.
You may see this error after you run the Tilesets CLI command to publish a tileset.
The problem could be that your tileset source is an empty file, or that it does not contain any line-delimited GeoJSON features. Check the tileset source to confirm that it contains valid features.
No GeoJSON features processed. Make sure your GeoJSON is line-delimited.
You may see this error after you run the Tilesets CLI command to publish a tileset.
This error is most common when a tileset source is a GeoJSON file, but is not line-delimited GeoJSON. MTS requires all tileset sources to be line-delimited to process correctly. You can learn more about the line-delimited GeoJSON format and some conversion tools in the Tileset sources guide.
No GeoJSON features to process.
You may see this error after you run the Tilesets CLI command to create a tileset.
The problem may be that your data was not uploaded. Check that the data was indeed uploaded.
You may also see this error if the filter in your recipe is failing for some reason. If you have a filter condition like [ "<=", [ "get", "minzoom" ], 5 ], and one or more of your features has a null value for minzoom, you could run into this error. You can use the coalesce operation in an expression to provide a default value to replace missing data. For instance, if you want a missing minzoom attribute to be treated as 0, you could write this expression as [ "<=", [ "coalesce", [ "get", "minzoom" ], 0 ], 5 ]. For more information on recipe filters, see the Recipe reference.