This sometimes happens to me if my wonky cluster decides to not behave. My original solution was to create a backup and then rebuild the cluster from this but I found a better solution in [[https://github.com/cloudnative-pg/cloudnative-pg/issues/4188#issuecomment-2912459078][this comment]:

I solved the issue.

1. You need to check the last history file on your primary ls -1 /var/lib/postgresql/wal/pg_wal/*.history. In my case it is /var/lib/postgresql/wal/pg_wal/00000015.history
2. Go to S3 storage and delete everything, which starts with next numbers: 00000016*, 00000017*, 00000018* and so on

Looks like it gets wrong history (which was canceled before) and fails