After clicking verify connection for git repository on rasa-x terminal, it continuously running and not getting stopped.
Logs of rasa-x container
Run time of job "run_background_synchronization (trigger: cron[minute='*'], next run at: 2022-05-05 06:00:00 UTC)" was missed by 0:00:02.749710
Run time of job "run_background_synchronization (trigger: cron[minute='*'], next run at: 2022-05-05 06:01:00 UTC)" was missed by 0:00:17.563057
Run time of job "run_background_synchronization (trigger: cron[minute='*'], next run at: 2022-05-05 06:02:00 UTC)" was missed by 0:00:19.794498
Run time of job "run_background_synchronization (trigger: cron[minute='*'], next run at: 2022-05-05 06:03:00 UTC)" was missed by 0:00:34.663922
Run time of job "run_background_synchronization (trigger: cron[minute='*'], next run at: 2022-05-05 06:04:00 UTC)" was missed by 0:01:03.837979
Run time of job "run_background_synchronization (trigger: cron[minute='*'], next run at: 2022-05-05 06:05:00 UTC)" was missed by 0:00:43.961763
Run time of job "run_background_synchronization (trigger: cron[minute='*'], next run at: 2022-05-05 06:06:00 UTC)" was missed by 0:00:25.242736
Run time of job "run_background_synchronization (trigger: cron[minute='*'], next run at: 2022-05-05 06:07:00 UTC)" was missed by 0:00:19.956411
ERROR:pika.adapters.blocking_connection:Unexpected connection close detected: AMQPHeartbeatTimeout: ('No activity or too many missed heartbeats in the last 60 seconds',)
Run time of job "run_background_synchronization (trigger: cron[minute='*'], next run at: 2022-05-05 06:08:00 UTC)" was missed by 0:00:11.189798
Run time of job "run_background_synchronization (trigger: cron[minute='*'], next run at: 2022-05-05 06:09:00 UTC)" was missed by 0:01:16.810067
Run time of job "run_background_synchronization (trigger: cron[minute='*'], next run at: 2022-05-05 06:10:00 UTC)" was missed by 0:00:49.077263
Run time of job "run_background_synchronization (trigger: cron[minute='*'], next run at: 2022-05-05 06:11:00 UTC)" was missed by 0:00:45.789269
I have to restart the docker-compose to stop this. What could be the issue here?