Issues with policy training, rasa 3.x (GraphConnection error)

Rasa Open Source
1

Hi there,

We’re working on policy training and getting this error when attempting to train the TED Policy:

File "/opt/venv/lib/python3.8/site-packages/rasa/engine/graph.py", line 465, in __call__
    raise GraphComponentException(
rasa.engine.exceptions.GraphComponentException: Error running graph component for node train_TEDPolicy1.

i’ve read a couple of past threads on people facing similar issues:

but we still can’t get the issue fixed. We have double checked that all intents are present in our config file, which was mentioned in one of the previous forums as a potential cause.

Policy config is as follows:

   - name: RulePolicy 
   - name: TEDPolicy
     max_history: None
     epochs: 100
     constrain_similarities: true

Is anyone else facing this issue, and if so, has a fix? Thanks

2

I faced this issue when one of my intent is not registered in domail.yml file under intents and I think it may occur if two different stories have same name also

1 Like
3

I am having the same issue here. Could someone help? Thanks

4

hello

did you find any solutions for this error?

6

Hello,

I am getting the same issue. Did anyone find a solution?

Thanks,

7

I could solve the mentioned error by adding all intents into the domain.yml file

10

this error is not about TEDPolicy1 or other pipelines. These kind of errors happen because of some wrong syntax in other files. I have solved this problem by changing my domain.yml file. from this:

actions:

  • utter_goodbye
  • utter_greet
  • utter_did_that_help
  • utter_cheer_up
  • utter_iamabot
  • utter_happy
  • action_reply_ask

to:

actions:

  • utter_goodbye
  • utter_greet
  • utter_did_that_help
  • utter_cheer_up
  • utter_iamabot
  • utter_happy
  • action_reply_ask

I think this kink of error happens because rasa can not link actions.py in actions file with that in domain.yml file

1 Like
11

The same worked for me. Thanks!

12

I don’t see difference in from and to. Please let know what changes you have done to resolve the issue.