Athena Iceberg Table is growing infinitely with the same number of rows.

I have an Iceberg Table which holds constant number of rows. Every hour I update some of this rows using MERGE command. After each MERGE I'm executing VACUUM command. Table is created with following properties.

TBLPROPERTIES (
  'table_type'='iceberg',
  'vacuum_max_snapshot_age_seconds'='60'
);

Initially this table is about a 1GB. In week or so it grows up to 50+ GB.

What I'm doing wrong? How to avoid this growth and delete unnecessary garbage?

UPDATE

It looks like the vacuum does not remove orphaned files. I have following settings

TBLPROPERTIES (
  'table_type'='iceberg',
  'vacuum_max_snapshot_age_seconds'='60',
  'vacuum_max_metadata_files_to_keep'='1',
  'optimize_rewrite_delete_file_threshold'='2',
  'optimize_rewrite_data_file_threshold'='2',
  'vacuum_min_snapshots_to_keep'='2'
)

I do vacuum hourly right after update.

My table has following partitions

PARTITIONED BY (`partition`, `pos`, `pcc`, hour(`requeststarted`)) 

And despite the fact than following query

select min(requeststarted), max(requeststarted) 
from estr_iceberg_latest_warehouse

gives following results

#	_col0	_col1
1	2024-07-22 11:04:55.347000	2024-07-30 10:57:38.610000

I still can see endless amount of data on S3 in directories like this 'requeststarted_hour=2024-05-31-02/' which way out of the bound of partition values.

Should I remove orphaned files from the S3 manually?