Clonable Template: Adressing non-existing Module ID should raise error

[benjamin-hinrichs]

When working with clonable modules it is possible (although not desired) to address a Module ID instance that doesn't exist (e.g. has already been closed, never existed in the first place). All clones would ignore said request and in the best case you'd see a timeout error. This may bring about unexpected bugs, especially when working with Requests (without reply).

I think the request should check if Module ID exists and throw an error if it doesn't. This could work by modifying the Request and Request with Reply template to the following:

I propose to add such functionality to the DQMH Clonable Template and check for this in module validation.

[Olivier-JOURDAN]

I was about to Kudo, but I'm worried about the overhead that could occur. I don't think this deserves it.

I get your use case, but I think it should be handle locally.