Why can't tasks be set during transactions?

Question

I just found out that transactional tasks cannot be called. Why is this? As if assigning names is an action in another group of entities, but the “unnamed” tasks are actually defined by the names generated by the api.

Answer 1

The task names are unique, so if you add a task with the name "foo", subsequent additions of tasks with the name "foo" will fail. This uniqueness check must be performed within the transaction itself, so all named tasks in the application must have the same entity group.

If you are trying to atomically put tasks into a transaction, then the tasks should have the same group of entities as other transactional entities, and the uniqueness check will not be reliable.