# 18-Mar-2026 — Orphaned booking detection and reassignment [#177](https://github.com/nbarrett/ngx-ramblers/issues/177)

## [build 543](https://github.com/nbarrett/ngx-ramblers/actions/runs/23237154453) — [commit 6cfcd53](https://github.com/nbarrett/ngx-ramblers/commit/6cfcd53583374cdd3c767849094d62fced4c804e)

_____

#  User Guide

When a booking's linked event is deleted or no longer exists, the **Admin → Bookings → Summary** page now identifies these as orphaned bookings and provides tools to fix them.

- Summary tab — Orphaned bookings appear highlighted in yellow with an Orphaned badge, making them easy to spot at a glance.



![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/ccef3783-6758-4a58-9ded-6d2593c23960.jpeg)


- Per-Event Detail tab — Selecting an orphaned entry from the event dropdown displays a warning panel explaining the situation. From here you can:
- Reassign bookings — Use the "Reassign bookings to" dropdown to pick a valid event, then click the Reassign button to move all affected bookings to that event. This is useful when an event was deleted and recreated (e.g. by the Walks Manager sync), and you need to reconnect existing bookings to the replacement event.


![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/bf9b7b49-38e6-4a32-b61a-f6d17d6024fa.jpeg)

- Delete individual bookings — If the bookings are no longer needed, use the delete button on each row to remove them.
- Attendee visibility — Even while orphaned, full attendee details (names, emails, phone numbers, booking date, and status) remain visible so you can verify who is affected before taking action.
* Select the event in the reassignment select and then click the **Reassign** button:

![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/2a8e2d83-a3fb-4fee-beb5-055df1aacf63.jpeg)

* Bookings will then show correctly assigned to an event:

![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/df73c5ee-70c8-4d3e-b4f6-1c1a7ec3e054.jpeg)