LISTEN - ERROR: could not access status of transaction 3021015672

Hello,

I've found in our server ( PostgreSQL 13.5 on x86_64-pc-linux-gnu, compiled
by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit ) following error:

2022-03-31 09:29:58 CEST [15490]: [1-1]
user=app,db=main,host=192.168.1.231,app=[unknown] ERROR: could not access
status of transaction 3021015672
2022-03-31 09:29:58 CEST [15490]: [2-1]
user=app,db=main,host=192.168.1.231,app=[unknown] DETAIL: Could not open
file "pg_xact/0B41": Adresář nebo soubor neexistuje.
2022-03-31 09:29:58 CEST [15490]: [3-1]
user=app,db=main,host=192.168.1.231,app=[unknown] STATEMENT: LISTEN
"CONFIG"

Since we have enabled track_commit_timestamp, I' tried:
prematch=# show track_commit_timestamp ;
track_commit_timestamp
------------------------
on
(1 row)

prematch=# select * from pg_xact_commit_timestamp('3021015672');
pg_xact_commit_timestamp
--------------------------

(1 row)

Since this was not helpful, searching in the archives, I've found the
thread:

"BUG #16961: Could not access status of transaction"
https://www.postgresql.org/message-id/flat/VE1PR03MB531295B1BDCFE422441B15FD92499%40VE1PR03MB5312.eurprd03.prod.outlook.com#7e36d1fdca921b5292e92c7017984ffa

But it looks not to have any result.
Unfortunately, I have no isolated test case, so I'd like to ask for advice
on what set of information to collect if it happened next time, to be able
to supply some valuable bug reports.
If it is a known configuration issue or an application logic issue, any
advice is welcome (the scenario described in the abovementioned thread is
not our application case).

Thanks, Ales