Automatically stop action after completion

I agree with @strawgate

Given your number of console operators and endpoints, I suspect an issue with the hardware of your BigFix root server / infrastructure. There could also be network latency issues between your console sessions and the root server. Generally you want the network connection between the console and the root server to be as fast and as low latency as possible.

What are the specs of the root server, in particular the storage backing the BFEnterprise DB and FillDB ?

With that few endpoints and operators, I find it highly unlikely that anything to do with open actions is the cause of slowness.

What behaviors are you experiencing in the console that are a problem? Can you describe it?

Also, I wouldn’t recommend doing this all of the time, but you can install the console on the root server itself and open it there. If you have the same console performance issues there, then the issue is not network related. ( though there can still be timeout issues )