In GPCC workload management tab, there is one function to setup a rule, then automatically terminate any idle connections based on this rule. But sometime users may find certain idle session is not controlled by this rule.
This is caused by gpcc workload management tab used a different way to define "IDLE" connections. It's start counting the idle time when one session finished executing one query. In other words, only those sessions that have been running any queries, it will fit in this rule. Any connection that didn't run any query since connected to the database is not controlled by this rule.
Users may setup their own script to automatically terminate all kind of idle connections if they want to include those never run any query connections.