Ambiguous, Invalid, or System Error?

Описание и применение

Внедрение новых состояний классификатора (неоднозначный, недействительный, системная ошибка) улучшило маршрутизацию запросов в автоматизированном агентстве.

Задача

The intake classifier needed distinct states for ambiguous, invalid, and system error to route requests appropriately.

Результат

The updated classifier correctly routes ambiguous, invalid, and system_error cases, preserving the reason for each decision and avoiding misleading client messages.

Рабочий процесс

• Define normal categories
• Add ambiguous state for overlapping categories
• Add invalid state with has_partial_intent boolean
• Add system_error state for classification failures
• Test with example requests
• Implement explicit Switch/IF routing
• Verify logging and email behavior

Доказательства

I exercised a deliberately ambiguous request, vague and out-of-scope inputs, and a forced model failure.

Источник

The workflow retried classification three times at five-second intervals, then reached the fallback route for human review.

Источник