Hi! Can you post your gcode file for me? Also, if you turn on the 'Position State' info panel in the tab, it gives more detailed info about the current state of Octolapse's position detection. My guess is that it doesn't know the XYZ axis mode, which seems common for CR-10 printers. They don't put a G90 in their default start-up gcode like they should IMO.
Look in your start/end gcode for a G90 command. If there is none, go into Octolapse and change 'XYZ Axis Mode' to 'Absolute' and try another test print. Without seeing your gcode that is my best guess.
FYI, I'm thinking of changing the default CR10 profile to deal with this issue. I've been resisting setting 'absolute' as the default since it's possible someone sends a G91 before your print starts, which would mess things up.
Also, take a look at this troubleshooting page, which could help too: https://github.com/FormerLurker/Octolapse/wiki/Troubleshooting
Let me know if that helps.