For our purposes, we put Rasa Core behind another service (business logic) that is not written in Python and handles several tasks like API calls, hand-off to a human agents, connecting to different channels etc. For that purpose, we treat Rasa Core (running in server mode) as a passive component that the business logic pushes to by using the /parse & /continue endpoints.
With Rasa Core 0.11, these endpoints have been removed and the migration guide says that
Instead of you calling Rasa Core to update the tracker and receive the next action to be executed, Rasa Core will call your action server once it predicted an action
Is it still possible to reconcile this workflow with our architecture? It seems that I could use /respond and update /tracker/events but this doesn’t seem to be a real solution because
- /respond is deprecated
- Rasa Core tries to contact the action server (which our model doesn’t have nor need)
- this approach contradicts the new direction since 0.11.
Now I wonder if or how we can still use Rasa Core as a component that waits to be called instead of it being the active “hub” of the architecture.