VTN restart causes loss of report registration context – request guidance #186

After restarting only the VTN (openleadr server), VENs continue to send oadrUpdateReport messages,
but the VTN no longer uses the wrapped_on_update_report callbacks previously negotiated,
and falls back to the generic on_update_report behavior without resolving r_id metadata.

This results in:

• loss of VEN, resource, measurement context
• need to persist mapping or force re-registration

Expected: guidance on recommended patterns for openleadr to handle VTN restart without requiring VEN re-register.

Testing environment:
openleadr version X.Y.Z

Steps to reproduce:

1. start VTN + VEN
2. register report (wrapped callbacks registered)
3. kill VTN
4. restart VTN
5. VEN continues polling and sending reports
6. VTN falls back to on_update_report

Desired: is there a supported way to force VEN re-registration or persist mapping?

Thank you.