Troubleshooting segmentation runs
Most segmentation run issues come from missing inputs, stale renders, overly broad prompts, patch limits, or backend availability. Start with the visible state in RasterForge before changing profile settings.
The run cannot start
Check that:
- The image has an AOI.
- The image has a current segmentation render.
- The selected segmentation profile still exists.
- Prompt text is within the current limit.
- Image guidance does not exceed the point and box limit.
- Find workflows using examples have at least one saved example.
- The daily patch meter has enough remaining patches.
The mask is poor
Inspect the render first. If the target is low contrast, adjust bands, stretch, gamma, NDVI settings, or AOI before changing thresholds. Then tune detection threshold, mask threshold, max instances, and postprocess settings.
If the layer has many false positives, narrow the prompt, add better examples, raise thresholds, reduce max instances, or reduce the AOI. If the layer misses real targets, check whether the target is visible in the render, lower thresholds carefully, or add more representative guidance.
The result looks stale
If the image, AOI, render recipe, render settings, or profile changed after a previous run, generate a fresh render and rerun segmentation. Layer snapshots may preserve older prompts and render choices so past results remain explainable.
GeoJSON update fails
GeoJSON recalculation needs the stored mask bundle and related artifacts. If a live re-export cannot access the required cached output, rerun segmentation or create a fresh layer before export.
The backend is unavailable
Retry after checking current account limits and run status. If failures continue, contact support with the project name, layer name, image name, approximate run time, and visible error message.