Timing failure: different clock delay for launch and latch clock

Can't tell from the screenshot. Go to the Details tab, and make sure you run report_timing with "-detail full_path", then look at the clock path and make sure it is on a global, and the same global. Assuming it's the same clock on a global, there is nothing you can do about it. There will be skew on globals, mainly due to on-die variation. Note that two nodes near each other can be at very different ends of the global H tree, and the less commonality they have resulting in more skew. Within a timing model, delays have a +/- delay. So for example, a section of the clock tree might have a delay of 1ns-1.2ns. During setup analysis the larger delay will be used for the launch clock and the slower delay for the latch clock. Common Clock Path Pessimism removal will remove this from any common portions of the clock tree since it can't be both slow and fast at the same time, but any non-common portions will not be removed.

Now, 900ps of skew seems large. I usually think over 500ps is where it gets suspicious. If they are not on the same global, then there could be multiple reasons for skew and it's hard to say without more details.