Exception raised while accessing last_round_transition_timestamp after tm sync

[dvilelaf]

When a behaviour or handler tries to access last_round_transition_timestamp during the first round (usually registration), an exception is raised:

 2025-02-14 12:34:16.738	2025-02-14T12:34:16.638333006Z stdout F   File "/root/agent/vendor/valory/skills/abstract_round_abci/base.py", line 3483, in last_round_transition_timestamp
2025-02-14 12:34:16.738	2025-02-14T12:34:16.638342776Z stdout F     raise ValueError(
2025-02-14 12:34:16.738	2025-02-14T12:34:16.638357006Z stdout F 
2025-02-14 12:34:16.738	2025-02-14T12:34:16.638368336Z stdout F ValueError: Trying to access `last_round_transition_timestamp` while no transition has been completed yet.

This

Explore-logs-2025-02-14 15_00_07.txt

happens during registration and comes from core somewhere, righ after tm synchronization