Issues with overnight DAP

Question

Hello!

Has anyone noticed slowness/failures in their DAP processes?

We use the incremental CLI from DAP overnight starting around 1 AM Arizona Time.  It was taking 15-20 minutes for a sync to occur.  Then around 4/17 to now it's taking over an hour.  Last night we even got 500 errors from the DAP Api and one of our other service updates returns Unauthorized "sometimes".

Does anyone know if they are doing maintenance overnight or something now?  I'm noticing lots of alter tables come through the sync process that makes it seem like they may be doing lots of schema upgrades.

Excerpt from the DAP Logs:

If not - I haven't actually ever had to submit a ticket or anything - what is the official channel to request support from them?

DanielMoore · Answer

Greetings from St Louis, group and @Gergely Schmidt . I have opened case (14141848) with Canvas Support; but also posting here as it relates to the same issue @pgentry has reported. We are experiencing the same issue, returning extended delays returning Query starts as shown below. We too began observing this the afternoon of Apr 27th, cst. Canvas Support initially responded to my case by pointing out last night's issue with weblog data latency. Noting that that process is catching up, I'm wondering if it is affecting the Canvas Namespace as well as the Canvas_Logs Namespace. I've posed that question back to Canvas Support also, but wanted to surface it here as well. The snippet below is an example from a job I executed this morning at 2026-04-29 08:06:31; as of now the job has sync'd 55 of 95 tables. That job normally runs out in ~45-90 min's. Python 3.13.2, DAP CLI 2.2.0. From command line in powershell 7, as administrator: dap --logfile dap.log syncdb --namespace canvas --table all 2026-04-29 10:51:50 931 - INFO - Query started with job ID: ~~50baf61d-00ac…………………..~~ 2026-04-29 10:51:50 939 - INFO - Query job still in status: waiting. Checking again in 5 seconds... 2026-04-29 10:51:56 193 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:52:01 437 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:52:06 598 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:52:11 857 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:52:17 207 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:52:22 381 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:52:27 584 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:52:32 739 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:52:37 962 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:52:43 157 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:52:48 438 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:52:53 595 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:52:58 767 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:53:03 918 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:53:09 058 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:53:14 361 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:53:19 579 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:53:24 758 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:53:29 935 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:53:35 167 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:53:40 311 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:53:45 457 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:53:50 647 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:53:55 845 - INFO - Query job still in status: running. Checking again in 5 seconds... 2026-04-29 10:54:01 023 - INFO - Query job still in status: running. Checking again in 5 seconds... Many thanks in advance for any thoughts. Dan Moore Support Specialist | Canvas System Administrator Enterprise (636) 949-4131 (o) dmoore3@lindenwood.edu Lindenwood University

stimme · Answer

@pgentry To report Canvas Data / DAP issues to Instructure Support, I typically click "Report a Problem" in the Canvas Help menu, start the Subject with "Canvas Data - " and start the message by saying, "Please escalate this to Canvas Data support." That typically works.

I used to send email to canvasdatahelp[at]instructure[dot]com. That may still work, too.

mclark19 · Answer

@pgentry There was an announcement of a number of schema changes for 4/27/2026, so that might be what you are seeing.