Skip to main content
New Idea

Connector jobs shouldn't run if there is already one running

Related products:CS Data Management & Integrations

darkknight

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.

 

 

6 replies

darkknight
Forum|alt.badge.img+4
  • Author
  • Expert ⭐️
  • 1978 replies
  • July 6, 2022

Also - need the ability to ABORT jobs...


ebell
Forum|alt.badge.img+1
  • Gainsight Employee ⭐️
  • 11 replies
  • June 7, 2024

Hey, 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.


 

darkknight wrote:

Also - need the ability to ABORT jobs...

 

Big upvote on giving users the ability to abort connector jobs themselves.


Stuart
Forum|alt.badge.img+3
  • Helper ⭐️⭐️
  • 144 replies
  • June 10, 2024

Got 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?


gangayetukuri
Forum|alt.badge.img
  • Gainsight Employee ⭐️
  • 4 replies
  • June 10, 2024

@Stuart , As far as “process multiple invocations of a same job sequentially and one at a time” is concerned, the design is in principle on the lines of upsert operation being supported which implicitly honours the Last-Execution-Date-Time. 

However, Skip job run and Abort job run options can be useful.


Ester.Memoli
Forum|alt.badge.img+8
  • Helper ⭐️
  • 87 replies
  • September 20, 2024

+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.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings