From: Iowan in MD/DC
I can tell you exactly what happened. This isn't a bug.
The TF began 12 hexes away from the target. That is too far to get there in one movement phase. You can see that your TF can move a maximum of 9 hexes in a single phase.
While you had it set to Cruise, I'm not sure that a bombardment TF wouldn't override this (they always go in at mission speed, I think).
Setting the target from 12 hexes away, as you did, means that 1 of 2 things will happen:
1) Your TF will pause at 1 mission speed's worth of movement away from the target (9 hexes in this case), or
2) Your TF will proceed to the target in a single day, in this case arriving after the second movement phase, which means that it doesn't have a chance to move again until the next night phase.
It matters which version of the game you are using, as my thread from years ago that you responded to triggered michaelm to make a slight fix in the code to correct an issue that was causing some bombardment TFs to not move full speed when they should have been moving full speed.
And finally, some general advice. When using bombardment TFs, do not set the target until you have moved the TF yourself to within 1 mission speed run away from the target (or closer; I often will close to within 6-7 hexes first if I can). This essentially ensures that the bombardment will go off exactly when and how you intend it to. One last piece to it is that sometimes, if you set Remain On Station while doing all of these same things, you can achieve a morning or daytime bombardment, which generally causes more damage.