Hey team! Has there been any update on this? I seem to have a similar problem. I've enabled PITR ~45 minutes ago, even did a full migration of data (~90 MB worth of data + indexes), I've seen the Postgres-PITR bucket grow, the logs seem to be archiving a WAL file every minutes, and to confirm a full backup has been done.

pgbackrest-watcher: running pgbackrest backup --type=full

[...] full backup size = 85.2MB, file total = 1491

backup command end: completed successfully (12953ms)

pgbackrest-watcher: backup --type=full completed

pgbackrest-watcher: pitr anchor emitted

[...]

pgbackrest-watcher: verifying S3 catalog has full backup

pgbackrest-watcher: catalog verified — full backup present in S3

pgbackrest-watcher: iteration: no action (last_full=1780684583, archived=4, failed=0, gap_marker=absent, gap_state=clear, last_full_failed=0, lag=0)

WALs are pushed every minute:

archive-push command begin 2.58.0: [pg_wal/000000010000000000000044] [...]

pushed WAL file '000000010000000000000044' to the archive asynchronously

archive-push command end: completed successfully (603ms)

Yet, I still get this error: