Best Answer

How long does it take to complete processing a Background Job?

  • 2 August 2022
  • 8 replies
  • 122 views
G
Rank
Userlevel 2
Badge +1

Newcomer here, fairly new to Docebo and definitely new to the community :).

As the subject says how log does it take to complete a background job?   In this particular case it is a job importing a CSV containing exactly three users that I will like to create in Docebo.

I have been waiting for over 5 hours now.  Is there a schedule?   What’s the average completion time of background job?   I would expect for something this small to execute a little quicker.

I did search the documentation, the Docebo University, this community, and Google at large but couldn’t find an answer.  

icon

Best answer by lrnlab 2 August 2022, 20:50

View original

8 replies

leilaishtayeh
Rank
Userlevel 2

It should not take much time at all (~2 mins max for a job this size is my guess).

Our platform hasn’t processed jobs all day today - I suggest submitting a ticket to support and checking your other background jobs.

lrnlab
Rank
Userlevel 7
Badge +7

It depends on how may jobs are running and the sizes of those jobs...ex: we have an instance that syncs with Salesforce every 15 min so any adhoc background jobs tend to have to be squeezed in between those syncs so they take a little longer...generally and under normal circumstances your jobs should not take 5 hours...did you check the results to see if the job is actually be applied? Perhaps it’s stalled. You can try aborting the job and staring it again.

Bfarkas
Rank
Userlevel 7
Badge +3

Yeah, like @lrnlab its a little complicated to give exact times, and depending on how many admins and power users you have running jobs, the queue becomes an important thing to keep an eye on. That being said there are definitely some other processes that run and can block one of these jobs from running for a period of time, all in attempts to mitigate system resources and keep everyone up in the cloud running along, but 5 hours is on the edge where I would be seeing if anything else is getting processed and if not, opening a support call asap otherwise it will clear on its own (I find most of these blocks clear naturally in 12-14 hours) and they tend not to be able to troubleshoot to prevent in the future then.

G

There is an open issue with background jobs right now. I just stopped in to see if there had been any progress posted and am now sad to be the one telling you this. Open a support ticket as soon as possible so it can be attached to this issue and hopefully it gets resolved soon.

G
Rank
Userlevel 2
Badge +1

My initial job was at the processing status for over 5 hours; this being my first background job ever I was clueless on what to expect. 

I did follow @lrnlab suggestion to just cancel and retry.  This time it did execute almost instantly!

Thank you all!!

BTW, how buggy will you say background jobs are?  Scale 1 to 10, 1 the least 10 the most :).  I know software and bugs go hand-in-hand, I am curious to harness you experience thus far.

Bfarkas
Rank
Userlevel 7
Badge +3

My initial job was at the processing status for over 5 hours; this being my first background job ever I was clueless on what to expect. 

I did follow @lrnlab suggestion to just cancel and retry.  This time it did execute almost instantly!

Thank you all!!

BTW, how buggy will you say background jobs are?  Scale 1 to 10, 1 the least 10 the most :).  I know software and bugs go hand-in-hand, I am curious to harness you experience thus far.

Ha, I think the answer to that is that the inconsistency is inconsistent, they are fine until they are not, and then they are fine again :)

dklinger
Rank
Userlevel 7
Badge +6

Wouldnt it be consistently inconsistent?

L
Rank
Userlevel 5
Badge +2

So, about the time this was posted, our region had a roadblock on background jobs. All jobs were stalled for me, and I think many others. Support released a fix, then I had to cancel my pending jobs and restart them for them to work. (Ticket 256138 for reference).

@GeorgeK You may have just had the misfortune of trying this at the wrong time.

 

*edit* @gr33n3 Just saw you also noted the same thing! Sorry for duplicating you. :)

 

Reply


Terms & ConditionsCookie settings