503 Service Unavailable in wasabi when prune job is running

Hello everyone.
There was a problem processing the task prune in wasabi.
Here is part of the log

2026-04-18 13:57:25.118 WARN CHUNK_FOSSILIZE Chunk a376b6624147da1d3a06804e77df345e3224b534a921a1463abc699db1903b2b is already a fossil
2026-04-18 13:57:25.163 WARN CHUNK_FOSSILIZE Chunk 0af50a962bfcb42f5d64d8f14e22b9cde682c19bc6e9eed823a712b611e5902a is already a fossil
2026-04-18 13:57:25.665 WARN CHUNK_FOSSILIZE Chunk 31e559755a209b04efdcc0d7e44a73b1264dc0d23012587517d8aac93449da57 is already a fossil
2026-04-18 13:57:27.494 WARN CHUNK_FOSSILIZE Chunk 060bff4d65ac77da6a3c335aa3ef6fa7b932566ef42203a9f3fc23bbd34cf66f is already a fossil
2026-04-18 13:57:27.537 WARN CHUNK_FOSSILIZE Chunk 52f57121ec9956e49f511d9adb025277c8881662726be99d5ce9e8d51f30a32b is already a fossil
2026-04-18 13:57:30.761 ERROR CHUNK_DELETE Failed to fossilize the chunk 2506f690ad0bc78a8d241bc9ce703f8c2b12fd35bb93305b6d969428c9f96fad: 503 Service Unavailable
Failed to fossilize the chunk 2506f690ad0bc78a8d241bc9ce703f8c2b12fd35bb93305b6d969428c9f96fad: 503 Service Unavailable

What could be the reason?

When i run check job some chunks is missed.

2026-04-18 14:00:37.883 INFO SNAPSHOT_CHECK All chunks referenced by snapshot 03_wassabi_backup at revision 601 exist
2026-04-18 14:00:38.338 INFO SNAPSHOT_CHECK All chunks referenced by snapshot 03_wassabi_backup at revision 602 exist
2026-04-18 14:00:38.338 ERROR SNAPSHOT_CHECK Some chunks referenced by some snapshots do not exist in the storage
Some chunks referenced by some snapshots do not exist in the storage

Wasabi being wasabi. Nothing unusual. Open support ticket with them. Not that it will
Help — but maybe if everyone files tickets they will do something about it after years of flakiness