The upgrade to Netbox 3.2 improves change logging:
https://docs.netbox.dev/en/stable/additional-features/change-logging/
or
https://netbox-next.wikimedia.org/extras/changelog/
We currently rely on DB backups, CSV export dumps or manual change to revert a production mistake, all are quite heavy in process.
As the new logging includes the "before" state of an object, maybe we could have a script that reverts a given change ID (not request UUID).
As explained in https://github.com/netbox-community/netbox/issues/9464 it's not always possible to revert a change but the script could maybe cover enough use cases to be useful.