Closed AIIX closed 4 years ago
intent_failure is sent when the intent service can't determine the intent using adapt or high confidence padatious match. The intent_failure is picked up by the fallback system so this is valid for the "how old is steve jobs" which is handled in the fallback-query skill.
If the fallback also fails it will emit complete_intent_failure
intent_failure is sent when the intent service can't determine the intent using adapt or high confidence padatious match. The intent_failure is picked up by the fallback system so this is valid for the "how old is steve jobs" which is handled in the fallback-query skill.
If the fallback also fails it will emit
complete_intent_failure
The skill that is handling the response is the wikidata skill in the above request not the fallback-query.
From debug above:
2020-03-03 21:22:41.883 | DEBUG | 24343 | mycroft.messagebus.service.event_handler:on_message:38 | {"type": "mycroft.skill.handler.start", "data": {"name": "WikidataSkill.handle_wikidata_age_intent"}, "context": {"client_name": "mycroft_listener", "ident": "1583232754.2725458-6062518786377171711"}}
It also seems that complete_intent_failure is not sent most of the times on failed query after falling back to fallback-unknown skill. Test: "Hey mycroft, mouse" or (any random single english word)
Complete intent failure is mainly sent when no skill at all not even fallback unknown able to catch the response. it will trigger the "please wait while I finish booting up" dialog
Seems like the wiki-data skill uses padatious intents and it's likely it doesn't get the high confidence score needed for direct matching so it's handled by the fallback system.
I'm closing this issue now, feel free to reopen if I'm mistaken.
Intent_failure is being sent on the message bus even on a valid query and response. Branch: dev
Try to provide steps that we can use to replicate the Issue