# Chitchat cannot be handled **URL:** \ **Category:** Rasa CALM\ **Created:** [February 13, 2025, 1:30pm UTC](https://forum.rasa.com/t/chitchat-cannot-be-handled/66210 "2025-02-13T13:30:34Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![PetrG](https://avatars.discourse-cdn.com/v4/letter/p/dbc845/32.png) [@PetrG](https://forum.rasa.com/u/PetrG)\ **Post date:** [February 13, 2025, 1:30pm UTC](https://forum.rasa.com/t/chitchat-cannot-be-handled/66210/1 "2025-02-13T13:30:34Z")
Hi. I’m trying to enable chitchat in my Rasa Pro CALM bot. I did exactly what is written here: [Chitchat and Small Talk](https://rasa.com/docs/rasa-pro/building-assistants/enable-chitchat/) , but after any chitchat message, I get the default “cannot handle” message as a response. I have - fully functioning Rasa CALM where everything else works well - Intentess policy set up in config.yml - rephrase turned on in endpoints.yml - working OpenAI key in the env In the logs I see the Chitchat() command is correctly predicted, but a bit later “cannot\_handle” pattern is triggered with reason “cannot\_handle\_chitchat”. Here is what I think is the relevant part of the logs: ```auto 2025-02-13 14:10:00 DEBUG rasa.shared.providers._ssl_verification_utils - [debug] ensure_ssl_certificates_for_litellm_non_openai_based_clients ssl_certificate=None ssl_verify=None 2025-02-13 14:10:00 DEBUG rasa.shared.providers._ssl_verification_utils - [debug] ensure_ssl_certificates_for_litellm_openai_based_clients ssl_certificate=None ssl_verify=None 2025-02-13 14:10:00 DEBUG rasa.shared.providers.llm._base_litellm_client - [debug] base_litellm_client.formatted_response formatted_response={'id': 'chatcmpl-B0SktHKKj9ujsDzIK1AXhZg0nTzLA', 'choices': ['ChitChat()'], 'created': 1739450235, 'model': 'gpt-4-0613', 'usage': {'prompt_tokens': 730, 'completion_tokens': 5, 'total_tokens': 735}, 'additional_info': None} 2025-02-13 14:10:00 DEBUG rasa.utils.log_utils - [debug] llm_command_generator.predict_commands.actions_generated action_list=ChitChat() C:\Users\PetrG\AppData\Local\miniconda3\envs\Chatbot-assistant\lib\site-packages\pydantic\main.py:314: UserWarning: Pydantic serializer warnings: Expected `CompletionTokensDetails` but got `dict` - serialized value may not be as expected return self. __pydantic_serializer__.to_python( 2025-02-13 14:10:00 DEBUG rasa.utils.log_utils - [debug] llm_command_generator.predict_commands.finished commands=[ChitChatAnswerCommand()] 2025-02-13 14:10:00 DEBUG rasa.engine.graph - [debug] graph.node.running_component clazz=RegexMessageHandler fn=process node_name=run_RegexMessageHandler 2025-02-13 14:10:00 DEBUG rasa.core.processor - [debug] processor.message.parse parse_data_entities=[] parse_data_intent={'name': None, 'confidence': 0.0} parse_data_text=how are you? 2025-02-13 14:10:00 DEBUG rasa.core.processor - Logged UserUtterance - tracker now has 4 events. 2025-02-13 14:10:00 DEBUG rasa.engine.runner.dask - Running graph with inputs: {' __tracker__': DialogueStateTracker(sender_id: a4870e22aff94850840a49e6947c7018)}, targets: ['command_processor'] and ExecutionContext(model_id='f4e31ef37a464f6b83d396a9ec864be2', should_add_diagnostic_data=False, is_finetuning=False, node_name=None). 2025-02-13 14:10:00 DEBUG rasa.engine.graph - [debug] graph.node.running_component clazz=FlowsProvider fn=provide_inference node_name=flows_provider 2025-02-13 14:10:00 DEBUG rasa.engine.graph - [debug] graph.node.running_component clazz=StoryGraphProvider fn=provide_inference node_name=story_graph_provider 2025-02-13 14:10:00 DEBUG rasa.engine.graph - [debug] graph.node.running_component clazz=CommandProcessorComponent fn=execute_commands node_name=command_processor 2025-02-13 14:10:00 WARNING rasa.dialogue_understanding.processor.command_processor - [warning] command_processor.clean_up_chitchat_command.replace_chitchat_answer_with_cannot_handle command=CannotHandleCommand(reason='cannot_handle_chitchat') defined_intentless_policy_in_config=True pattern_chitchat_uses_action_trigger_chitchat=True 2025-02-13 14:10:00 DEBUG rasa.dialogue_understanding.processor.command_processor - [debug] command_processor.clean_up_commands.final_commands command=[CannotHandleCommand(reason='cannot_handle_chitchat')] 2025-02-13 14:10:00 DEBUG rasa.engine.runner.dask - Running graph with inputs: {' __tracker__': DialogueStateTracker(sender_id: a4870e22aff94850840a49e6947c7018), ' __endpoints__': }, targets: ['select_prediction'] and ExecutionContext(model_id='f4e31ef37a464f6b83d396a9ec864be2', should_add_diagnostic_data=False, is_finetuning=False, node_name=None). ``` No idea what’s wrong and how to make it work… Thanks much for any help. ---
**Author:** ![PetrG](https://avatars.discourse-cdn.com/v4/letter/p/dbc845/32.png) [@PetrG](https://forum.rasa.com/u/PetrG)\ **Post date:** [February 13, 2025, 4:36pm UTC](https://forum.rasa.com/t/chitchat-cannot-be-handled/66210/2 "2025-02-13T16:36:37Z")
According to info here - [Conversation Repair](https://rasa.com/docs/rasa-pro/concepts/conversation-repair/#9-cannot-handle) : \*\* The pattern [`pattern_cannot_handle`](https://rasa.com/docs/rasa-pro/concepts/conversation-repair/#reference-default-pattern-configuration) has the context attribute `reason`. `reason` is set to: - `cannot_handle_chitchat`, when [`pattern_chitchat`](https://rasa.com/docs/rasa-pro/concepts/conversation-repair/#5-chitchat) attempts to invoke `action_trigger_chitchat` without an `IntentlessPolicy` defined.\*\* But I have IntentlessPolicy in my config.yml and the logs from `rasa train` suggest it is correctly trained: ```auto 2025-02-13 14:54:06 INFO rasa.engine.training.hooks - Starting to train component 'IntentlessPolicy'. 2025-02-13 14:54:07 INFO rasa.core.policies.intentless_policy - [info] intentless_policy.training.completed 2025-02-13 14:54:08 INFO rasa.engine.training.hooks - Finished training component 'IntentlessPolicy'. ``` ---
**Author:** ![mnchs12312321](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@mnchs12312321](https://forum.rasa.com/u/mnchs12312321)\ **Post date:** [February 19, 2025, 8:20pm UTC](https://forum.rasa.com/t/chitchat-cannot-be-handled/66210/3 "2025-02-19T20:20:52Z")
Commenting to share that I am facing the exact same issue after following the documentation. Have you found a solution yet or is this still an issue? I am limited to using Rasa 3.10 but would good to know if it’s also an issue with later versions. ```auto 2025-02-19 15:13:55 WARNING rasa.dialogue_understanding.processor.command_processor - [warning] command_processor.clean_up_chitchat_command.replace_chitchat_answer_with_cannot_ handle command=CannotHandleCommand(reason='cannot_handle_chitchat') defined_intentless_policy_in_config=True pattern_chitchat_uses_action_trigger_chitchat=True ``` ---
**Author:** ![PetrG](https://avatars.discourse-cdn.com/v4/letter/p/dbc845/32.png) [@PetrG](https://forum.rasa.com/u/PetrG)\ **Post date:** [February 20, 2025, 6:58am UTC](https://forum.rasa.com/t/chitchat-cannot-be-handled/66210/4 "2025-02-20T06:58:55Z")
Nope. I tried everything that I thought might be relevant - no success. Also couldn’t find any relevant info on this anywhere else. I’m on Rasa 3.10.7. Currently I have a workaround, where I use a “chitchat” flow instead - this handles at least the most frequent cases of user chitchat messages in a simple manner. Would be grateful if you let me know in case you solve this. ---
**Author:** ![mnchs12312321](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@mnchs12312321](https://forum.rasa.com/u/mnchs12312321)\ **Post date:** [February 20, 2025, 7:54pm UTC](https://forum.rasa.com/t/chitchat-cannot-be-handled/66210/5 "2025-02-20T19:54:24Z")
@Arjaan can you please advise when we can expect support on this issue? This thread is now a week old and following the official Rasa documentation has been insufficient. ---
**Author:** ![shellka](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@shellka](https://forum.rasa.com/u/shellka)\ **Post date:** [March 1, 2025, 4:05am UTC](https://forum.rasa.com/t/chitchat-cannot-be-handled/66210/8 "2025-03-01T04:05:13Z")
Do you found how to fix it ? 😬 ---
**Author:** ![PetrG](https://avatars.discourse-cdn.com/v4/letter/p/dbc845/32.png) [@PetrG](https://forum.rasa.com/u/PetrG)\ **Post date:** [March 5, 2025, 7:16am UTC](https://forum.rasa.com/t/chitchat-cannot-be-handled/66210/9 "2025-03-05T07:16:33Z")
Nope. Could please someone from Rasa comment on this? I’m clearly not the only one having this problem and the documentation is not sufficient on this. ---
**Author:** ![mnchs12312321](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@mnchs12312321](https://forum.rasa.com/u/mnchs12312321)\ **Post date:** [March 5, 2025, 1:55pm UTC](https://forum.rasa.com/t/chitchat-cannot-be-handled/66210/10 "2025-03-05T13:55:51Z")
@PetrG I tried tagging the person who wrote the pinned post saying Rasa devs monitor these threads daily. I suggest tagging others if you know any ---
**Author:** ![PetrG](https://avatars.discourse-cdn.com/v4/letter/p/dbc845/32.png) [@PetrG](https://forum.rasa.com/u/PetrG)\ **Post date:** [March 19, 2025, 10:14am UTC](https://forum.rasa.com/t/chitchat-cannot-be-handled/66210/11 "2025-03-19T10:14:27Z")
@ChrisRahme : Would you perhaps know how to solve this…? Looks like more people face the same issue and we’re not getting any help here.. Thanks.. ---
**Author:** ![m\_ashurkina](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/m_ashurkina/32/25068_2.png) [@m\_ashurkina](https://forum.rasa.com/u/m_ashurkina)\ **Post date:** [March 20, 2025, 9:50am UTC](https://forum.rasa.com/t/chitchat-cannot-be-handled/66210/12 "2025-03-20T09:50:27Z")
Hi all, thank you for raising this issue and sorry for making you wait, I’ll check with the Rasa team what’s the best way to solve it and come back to you shortly, Marina ---
**Author:** ![m\_ashurkina](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/m_ashurkina/32/25068_2.png) [@m\_ashurkina](https://forum.rasa.com/u/m_ashurkina)\ **Post date:** [March 20, 2025, 1:36pm UTC](https://forum.rasa.com/t/chitchat-cannot-be-handled/66210/13 "2025-03-20T13:36:26Z")
Hi @PetrG @mnchs12312321 @shellka thanks again for raising this issue. This is a bug and it has been reported. This bug is triggered when IntentlessPolicy is used AND there is no e2e tests. If you want to continue using IntentlessPolicy there is a workaround: please create an e2e test, here is the link to docs how to do it: [Evaluating Your Assistant (E2E Testing) | Rasa Documentation](https://rasa.com/docs/pro/testing/evaluating-assistant/#:~:text=To%20run%20the%20end%2Dto,default%20path%20is%20tests%2Fe2e_test_cases). Please let me know if you still encounter the issue. Marina ---
**Author:** ![carlojanssens](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/carlojanssens/32/25092_2.png) [@carlojanssens](https://forum.rasa.com/u/carlojanssens)\ **Post date:** [March 30, 2025, 2:08pm UTC](https://forum.rasa.com/t/chitchat-cannot-be-handled/66210/14 "2025-03-30T14:08:10Z")
I am still having the same issue here.