Certain names unavailable for messages (DEF-2406)

Bugs
1

There seems like there are a bunch of reserved message names in the system, which makes it so that you get an error about missing parameters if you try to send the message, even though you are not sending the message to a receiver that requires those parameters with that message.

Since the message still works like I intend it to, if I supply the parameter (which I don’t need for my intention), this should be considered a bug and fixed.

2

We have opened a technical design ticket to discuss this issue internally (DEF-2406). It will take a while before we will be able to make a decision on the matter. For now the recommendation is simply to stay away from any message_id defined in the API documentation.