Global Slot Mapping or init payload brings conversation to crash in deployment

Hi all,

in my RASA bot that works perfectly locally but crashes in deployment. There are two possible reasons for the crash but I’m not able to tell which one is the case. Either it is caused by my Global Slot Mapping which has really a lot of tracking going on (and is running every bot/user turn). The other one is that I am sending an init payload from the HTML page to start the conversation and to track a user id that I get from the URL. These are the logs in DEBUG mode and maybe someone can point me to what is causing the problem:

2022-11-23 12:17:19.84 rasa-server session_started_metadata: None
2022-11-23 12:17:19.84 rasa-server2022-11-23 12:17:19 DEBUG rasa.core.processor - Logged UserUtterance - tracker now has 4 events.
2022-11-23 12:17:19.84 rasa-server2022-11-23 12:17:19 DEBUG rasa.core.actions.action - Calling action endpoint to run action 'global_slot_mapping'.
2022-11-23 12:18:15.92 rasa-server/usr/local/lib/python3.7/site-packages/aiohttp/ ResourceWarning: Sending a large body directly with raw bytes might lock the event loop. You should probably pass an io.BytesIO object instead
2022-11-23 12:18:15.92 rasa-server **kwargs,
2022-11-23 12:18:15.93 rasa-serverResourceWarning: Enable tracemalloc to get the object allocation traceback
2022-11-23 12:18:15.93 rasa-server2022-11-23 12:18:15 DEBUG rasa.core.lock_store - Deleted lock for conversation '9aa5f375-86b1-498b-afac-7802fcc165dd'.
2022-11-23 12:18:15.93 rasa-server2022-11-23 12:18:15 ERROR - Message handling timed out for user message '/greet{"id": "null"}'.

Note that it is not necessary that the ID is filled with something, so null will still work as nothing depends on this in the conversational flow.

To give some more details that may be relevant I use MongoDB (Mongo Atlas) as Tracker Store and talk to the bot through REST webhook.