the bug is, that this connection having the error is created at all. This connection should only be created if the second task is in a pool.
This only happens if you use the "fast modelling bar".
If your second task is located e.g. in a pool, that the connection can be created.
Thank you very much for clearing this up for me.
I will use data objects for information flowing between tasks in different lanes, and messages for information flowing between tasks in different pools.