[ykarkason]

Exactly the same thing happened to us in the Israel Regional, and after a lot of research we actually figured out why it happened to us:

We retrieved the speed for our shooter to spin from the driver station with NetworkTables, and it seems as if on the field it only starts to transmit NetworkTables data when they start the game(in a regular situation it starts sending the values as soon as the driver station connects to the robot) - this caused the robot to think he didn't have to spin the wheels, and because the encoders showed him he was within the tolerance - the acsenter in our robot started to push the Frisbee towards the wheels - but the wheel didn't spin, so the Frisbee got stuck, eventually the robot did receive the value, (but it seems as if the wheels in our shooter doesn't have much torque, and it wasn't enough to shoot the frisbee), but the front wheel did spin, as it got the speed it should spin in.
And so we lost that game - as our robot could not shoot, and we just had to give up autonomous.

I discovered that this is the reason because one of the teams from our regional played in the DC regional and the same miscommunication on the start of the match happened to them as well - the solved it by adding a two seconds delay in start of the autonomous.

To verify that the same thing happened to you, do you use NetworkTables to put crucial data to the robot?