Debugging Hanging Compress_Chunk operation

Hi All!

Requesting any advice / assistance for debugging a hanging compress_chunk policy / operation.

mydb=# SELECT * FROM pg_stat_activity WHERE state = 'active';
 datid | datname | pid  | leader_pid | usesysid | usename  | application_name | client_addr | client_hostname | client_port |         backend_start         |          xact_start           |          query_start          |         state_change          | wait_event_type | wait_event | state  | backend_xid | backend_xmin | query_id |                                 query                                  |  backend_type
-------+---------+------+------------+----------+----------+------------------+-------------+-----------------+-------------+-------------------------------+-------------------------------+-------------------------------+-------------------------------+-----------------+------------+--------+-------------+--------------+----------+------------------------------------------------------------------------+----------------
 17745 | mydb    | 8540 |            |       10 | postgres | psql             |             |                 |          -1 | 2022-11-18 13:23:48.121058-05 | 2022-11-18 13:23:48.691075-05 | 2022-11-18 13:23:48.691075-05 | 2022-11-18 13:23:48.691078-05 |                 |            | active |             |       723835 |          | SELECT * FROM pg_stat_activity WHERE state = 'active';                 | client backend
 17745 | mydb    | 7586 |            |       10 | postgres | psql             |             |                 |          -1 | 2022-11-18 13:13:36.125121-05 | 2022-11-18 13:19:54.488326-05 | 2022-11-18 13:19:54.488326-05 | 2022-11-18 13:19:54.488328-05 | Extension       | Extension  | active |      724054 |       723835 |          | SELECT compress_chunk('_timescaledb_internal._dist_hyper_3_63_chunk'); | client backend
 17745 | mydb    | 7574 |            |       10 | postgres | psql             |             |                 |          -1 | 2022-11-18 13:13:30.878554-05 | 2022-11-18 13:13:48.928725-05 | 2022-11-18 13:13:48.928725-05 | 2022-11-18 13:13:48.928727-05 | Extension       | Extension  | active |      723835 |       723835 |          | SELECT compress_chunk('_timescaledb_internal._dist_hyper_3_51_chunk'); | client backend

They are showing as active, but then never complete. Found this out after inspecting my compression_policy that had been running for several days and never succeeded.

Any advice appreciated!
Thanks