Incorrect call to action_session_start when sending intent / session_start

Rasa Open Source
1

When the intent /session_start is called, the default action_session_start is called. Then Rasa again calls action_session_start, which is triggered by the intent /session_start.

We are using a custom action-server written in java.

We are using a custom implementation of action_session_start. In this action, we get data from tracker.slots.session_started_metadata. The first time this action is called, the metadata is filled in correctly. When called again, this session_started_metadata slot is empty.

Where do we need to get the metadata on the second call?

2

Then Race again calls action_session_start , which is triggered by the intent /session_start .

What is Race referring to?

Where do we need to get the metadata on the second call?

is there new metadata for the second call or do you want to get the old metadata value?

3

I apologize for the stupid mistake, I mean Rasa, of course. I have corrected the topic body.

I would like to get the old metadata value. In addition, it seems more logical to me that action_session_start should not be called twice in this case.