Can connection pool timed out leads to 100% CPU utlization os it is independent?

I suspect that the connection pool issue is more the symptom of another issue than the root cause. There is something running wild doing all these connections and queries. This is what I would try to identify.

But, in case I repeat myself, more details result in better tips and recommendations.

We are writing into Db and whcih is causing Record sync but Appian process is writing more than 500 rows via different process intances and that is cauing connection pool drained out. Which is leading to many failed instance with large data and those must be utilizating CPU and leading to 100%. That is why asked if this understanding is correct or not.

I reiterate my earlier recommendation (from your other thread here) that you consider batching your writes differently and/or timing some of them such that you're not writing 600 separate ones all at once in different process instances.

I reiterate my earlier recommendation (from your other thread here) that you consider batching your writes differently and/or timing some of them such that you're not writing 600 separate ones all at once in different process instances.