Hi @Miguel Pereira,
The error here is coming from what labels you are using in your task sequence. There actually are no labels so the loading task doesn't know what to reference which makes it break. You can see what labels are assigned by clicking on the tokens or batch (2/10). If there were labels assigned to these tokens they would appear where the blue line is:

Also, tasks like this where the plane waits for a group of items is great for lists which was the way I was able to get your model to work (which is the image below). It works by sending putting the bags waiting in the queue on the list. The plane only pulls the bags off the list when there are 10 bags. It will then go through its sequence of loading and unloading the bags before starting over.. Be sure to go through each activity to see how it works. That way you can change the current labels to something that makes more sense to you (the labels are a little tricky when it comes to the sub flows so play around with it until you see how it's working).
testeaviaoagv (1).fsm
For your second question, each AGV group needs to be separated by a different process flow if you want them to act independently. This can be done by adding another AGV Process Flow:
Then duplicate the Global List "AGVWork" in the toolbox menu and call it something new.

You also need to go into the new process flow (AGV2) and find where it says "Global Load List" to change the list to the new one. This should free up your AGV groups to move independent of the other.
