Executed Service Node registration command more than 2 weeks late

[Fiftyw3bs]

Hi all, I'm not sure if this is the right place to ask this question, but I'm desperate.

I tried registering a service node, but I wasn't aware (aka, didn't read up to the paragraph) of the 2 weeks limit for the execution of the command for registration. I had saved the command somewhere, while waiting for my staked tokens to be unlocked.

It's now been about 12 hours since I executed the command and my tokens locked. But my Session Node is obviously not registered, as running the below command explicitly states the following:

$ oxend print_sn_status
2024-12-30 17:36:58.232	I Oxen 'Wistful Wagyu' (v10.6.0-2~ubuntu2204)
No service node is currently known on the network: xxxxxx

I was wondering if this means that my tokens are locked in limbo - never to be recovered. Or there's something that can be done to reverse this mistake.

Thanks.