When the endpoint is renamed an "update" event is emitted for all of the endpoint's checks. However as the checks themselves were never changed their "updated" timestamp is unchanged. When the probes receive the "update" event they compare the the "updated" timestamp of the check with the current running check definition and only refresh data if the timestamp has changed.
Solution:
when the endpoint.slug changes we need to modify the "updated" timestamp for all of the endpoint's checks.
When the endpoint is renamed an "update" event is emitted for all of the endpoint's checks. However as the checks themselves were never changed their "updated" timestamp is unchanged. When the probes receive the "update" event they compare the the "updated" timestamp of the check with the current running check definition and only refresh data if the timestamp has changed.
Solution: when the endpoint.slug changes we need to modify the "updated" timestamp for all of the endpoint's checks.