SIS_Import end job

[mlewis23]

We have a hung sis_import on our Canvas test server.  Anyone know how to end a sis_import job?

[shane_ohara]

Same here - open a case with Support and reference my case number (Case #01305669) as this tells me it is a bigger issue!

Shane

[mlewis23]

 @shane_ohara ​

Interestingly, I just got back a response to our ticket.  They said we have to wait 24 hours before they will escalate this on to the next level.  Hard to find anything acceptable about that response since no new imports can run until that one gets cleared out. Is that what they told you with your case?

[shane_ohara]

Yes, that is interesting. They told me that it was going to be escalated and according to the case in Service Cloud, it is at L2 now....still no response, but at least there. Definitely not an acceptable response. IMHO, I would reach out to your CSM and lodge a complaint.

[mlewis23]

Yep already contacted.  We don't have time to step through each level of help ticketing.

Ideally, there would be an api option to end the process ourself and not rely on Canvas to do it for us.  Although, I am interested in know why it stopped working.

[shane_ohara]

My SIS import finally finished and here's what I got back late last night:

"Thanks again for getting in contact with us.  The test server is really backed up right now so this likely won't complete for a day or two.  Our Devops team is working to get this back up to speed.  I see that it already worked in beta and prod for you so I can't suggest any workarounds.

Is there a certain reason you're trying to import this?  Is there something you're testing or any questions that you have regarding the import?"

I guess "testing" in test wasn't a valid reason to complain..?? LOL

[mlewis23]

For us, they waited long enough for things to start running on there own again.  It took about 11 hours for some of the imports to start.  They did however confirm our suspicion about limited resources within the response to our ticket:

"Because TEST is a testing instance, it doesn't have as many resources so it runs a bit slower which is why the import process took a little bit to finish. This also can be affected by traffic of other institutions utilizing TEST at the same time."

Although this response suggests that the resources for Test are different than for Prod and Beta, my guess is that when it comes to the sis_imports they are all tied together. Why they couldn't cancel a problem import or add resources on the fly is a mystery to me.  But fortunately for us, both Prod and Test are now functioning again.

[shane_ohara]

I laugh only because my SIS import was 1KB in size....it should NOT take 24+ hours to process in a test environment. My environment is still hosed...I have a course import still queued up now. I guess I'll just start "testing" in beta.

[mlewis23]

"Is there a certain reason you're trying to import this?" is now one of my favorite responses I've seen from Canvas Help.

I feel your pain.

[shane_ohara]

...and everything is back to normal now. I like normal.

[garth]

I have had a similar experience in both beta and test.

My understanding is that both of those environments are aggregate, multiple clients consuming the same workflow engine.  So if you have a customer testing large data sets it can cause the queue to become congested.  This scenario has caused long delays in my testing and has been a source of frustration for sure.

I am not aware of an API call to cancel an import.