I’ve run into this multiple times in the past - and running into it again now.
I have multiple copies of Connector jobs running, and because of something (still unsure of the cause - on chat with support right now) multiple jobs are stacking on top of one another, further exacerbating the problem.
If a Connector job is already running, the system should not launch a second iteration of the job. Wait until the running job is complete before launching another.
