2023-10-04 19:05:09 INFO rasa.cli.train - Started validating domain and training data…
YamlValidationException: Failed to validate ‘C:\chatboot\domain.yml’. Please make sure the file is correct and all mandatory parameters are specified. Here are the errors found during validation:
in C:\chatboot\domain.yml:5:
Cannot find required key ‘mappings’. Path: ‘/slots/name’
in C:\chatboot\domain.yml:7:
Cannot find required key ‘mappings’. Path: ‘/slots/email’
CAN ANYONE HELP WITH THIS ERROR
MY DOMAIN.YML CODE :
version: “3.1”
slots:
name:
type: text
email:
type: text
intents:
greet
goodbye
affirm
deny
mood_great
mood_unhappy
bot_challenge
email_id
user_name
responses:
utter_askname:
- text: “Please enter your name”
utter_askemail:
- text: “Please enter your email id to receive updates”
2023-10-06 22:14:28 ERROR rasa.core.processor - Encountered an exception while running action ‘action_email’.Bot will continue, but the actions events are lost. Please check the logs of your action server for more information. Traceback (most recent call last): File “c:\users\satheesh bhukya\appdata\local\programs\python\python38\lib\site-packages\rasa\core\actions\action.py”, line 780, in run response: Any = await self.action_endpoint.request( File “c:\users\satheesh bhukya\appdata\local\programs\python\python38\lib\site-packages\rasa\utils\endpoints.py”, line 175, in request raise ClientResponseError( rasa.utils.endpoints.ClientResponseError: 404, Not Found, body=‘b’{“error”:“No registered action found for name ‘action_email’.”,“action_name”:“action_email”}‘’
The above exception was the direct cause of the following exception:
Traceback (most recent call last): File “c:\users\satheesh bhukya\appdata\local\programs\python\python38\lib\site-packages\rasa\core\processor.py”, line 960, in _run_action
events = await action.run( File “c:\users\satheesh bhukya\appdata\local\programs\python\python38\lib\site-packages\rasa\core\actions\action.py”, line 810, in run raise RasaException( rasa.shared.exceptions.RasaException: Failed to execute custom action ‘action_email’ can you resolve