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.
+4Also - need the ability to ABORT jobs...
+1Hey, 100% agree with the above point. Had a situation come up with a client where the ability to abort job would have saved them hours.
Also - need the ability to ABORT jobs...
Big upvote on giving users the ability to abort connector jobs themselves.
+3Got my upvote, I’m interested in hearing from the PM/engineering team on the thought process of allowing multiple iterations of the same connector job running (or at least trying to run) simultaneously. Also, we can abort rules for data pull/push, so why not connectors? Is this an oversight on design, or is there functionality blocking the option to abort jobs?
However, Skip job run and Abort job run options can be useful.
+8+1 to the ability of aborting a connector job. It’s insane you cannot stop it, in case you launched something even by mistake in a test phase.
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
