Skip to main content

Troubleshooting common Autocriteria failure cases

Troubleshooting Autocriteria Failure Cases

K
Written by Kevin Wagner
Updated over a year ago
  1. Autocriteira is not available on the event/venue level (most common): Either the model is not trained on this venue or there is some other mapping issue causing autocriteria not to be available. In these cases, Autocriteria will not be available for any of the listings within the event. In these cases the Autocriteria Button will not be present below the map.

2. Unsupported sections: Within the venue, there are some sections that will have no coverage available. This is most likely due to insufficient data from those sections. In these cases, we do not allow AC to be set on those sections as the base or those sections to be included in the suggestions.

Unsupported sections will be shown in two ways. On the map, they will be highlighted white with gray striping across them. When hovered over, there will be a tooltip marking the section as unsupported and the header will be red instead of navy.

3. Unmapped Listings: To apply autocriteria, listings need to be mapped back from their section listed in the POS to their section on the exchange map. There are cases where naming conventions cause listings not to map back. In these cases users can select the proper base section on the map. For more information, see the section overrides section.

Did this answer your question?