The Night Canvas Went Down: A Real Journey Thread
A real thread from the night Canvas went down with a paper due. What a good reply does under a deadline, and the outage questions campus staff can answer before the next one.
Key takeaways
- Under a deadline, a good reply is a short list of moves in the right order, starting with "not your fault".
- The most useful advice in an outage is a paper trail: email the professor from the school account, attach the work and a screenshot of the outage.
- A ten-minute outline turns "i don't even know what it's supposed to be" into a start.
- Never promise what a professor will do. Help the student ask for an extension well, and let the professor decide.
- Outages near a deadline produce the same handful of questions every time, and campuses can write the answers in advance.
It's a night in May, the last stretch of the spring term. A reflection paper is due tonight, and the study guide for a history class lives on Canvas. Canvas is down. The student texts Journey. Here's the thread.
JourneyText Message
A night in May
canvas is down and my reflection paper is due tonight. and the history study guide is on canvas
that's a legit mess and not your fault. email both professors now: canvas outage, ask for an extension or another way to submit. send the paper as a PDF by email. for history, use your notes and the lecture slides, and ask for the study guide by email.
i don't even know exactly what the reflection is supposed to be
start anyway. 10-min outline: the prompt, three points, one example each. then write a messy first draft fast and clean it once. screenshot canvas being down as proof.
the syllabus might say
the syllabus usually has the length and format even when canvas is down. still email him. a slow reply beats no paper trail. send it from your school email with the screenshot attached.
A real Journey thread, shortened, with details changed so the student can't be identified.
Six messages in, the student has two emails to send, a screenshot to take and a ten-minute task to start. Nothing in the replies is clever. Under a deadline, a good answer is a short list of moves in the right order, and this one gets the order right.
What the replies got right
It said "not your fault" first
A student staring at an error page the night a paper is due assumes the worst: the paper will be late, and the professor will think the outage is an excuse. Taking blame off the table before giving any instruction is kind, and it's also practical. A student who feels accused writes a defensive email, or none at all.
It built a paper trail
Email both professors now. Send the paper as a PDF. Screenshot the outage. Send from the school account, with the screenshot attached. Each step creates a timestamped record that the work existed and the student tried to submit it. "a slow reply beats no paper trail" may be the most useful sentence in the thread, and it's worth teaching every first-year before their first deadline.
It shrank the task to a ten-minute start
"i don't even know exactly what the reflection is supposed to be" is the sound of someone about to give up for the night. The reply doesn't explain what a reflection paper is. It hands over a ten-minute outline (the prompt, three points, one example each), then a fast, messy draft and one clean pass. Starting is the hard part, so the reply makes starting small.
It pointed at the syllabus, and kept the email
Students forget the syllabus exists outside the learning management system, though plenty have a copy from week one in their downloads or inbox. The student half-remembered it, and the reply confirmed it: length and format are usually there. Then it added "still email him," so the syllabus didn't become a reason to skip the paper trail.
It didn't promise what a professor would do
The first reply says to ask for an extension or another way to submit. Journey can't grant an extension and shouldn't imply one. Extensions are the professor's call. Journey's job is to make the request quick, polite and documented, and to get the student writing while they wait.
What it left out
No paragraph of sympathy before the first instruction. No troubleshooting: the outage wasn't the student's to fix, but the submission was. No clarifying questions before helping; the first reply already had everything needed to act. And no prediction about how the professors would respond, which nobody texting at night can know.
The outage questions to prepare for
An outage near a deadline produces the same handful of questions every time, and because deadlines cluster at 11:59 PM, they arrive when the offices with the answers are closed. You can write the answers now.
| What students ask | The answer to have ready | Who owns it |
|---|---|---|
| "is it down for everyone or just me" | Where the campus posts outage notices, and the platform's status page if it has one | IT |
| "how do i turn it in" | The campus guidance for submitting during an outage, usually an email to the instructor from the school account with the file attached | The provost's office or teaching center, with faculty |
| "will i get an extension" | That it's the instructor's decision, plus any campus guidance on outages | Faculty |
| "where's the syllabus" or "where's the study guide" | Where course materials live outside the LMS, if anywhere | Faculty |
| "who do i tell" | The help desk's contact details and after-hours coverage | IT |
If your campus has no written guidance for outages near deadlines, the week after one is a good time to write it. It can be three lines: email the instructor from your school account, attach the work and a screenshot, and the instructor decides the rest.
What faculty can do before the next one
- Send the syllabus as a PDF by email in week one, so it survives an outage.
- Add one sentence to the syllabus saying what to do if the LMS is down at a deadline.
- Announce by email when it happens, since the LMS is the thing that's down.
- Answer the outage email, even with one line. "got it, you're fine" ends a student's night.
What Journey can do on a night like this
Journey texts students first and answers when they text back, at any hour, over ordinary SMS or iMessage, with nothing to install. Its answers to campus questions come from the resource base gathered at setup, so if your outage guidance and help desk hours are in it, the next student who texts during an outage gets them in the first reply. Journey doesn't contact professors or decide anything about extensions. It helps the student ask well, and start.
Outages are rare and deadlines aren't, so the two will overlap again. When they do, students will ask the same few questions, and the answers can be ready.
Frequently asked questions
What should a student do if Canvas is down when an assignment is due?
Email the instructor right away from the school account, explain the outage, attach the work as a PDF and a screenshot showing the outage, and ask whether there's another way to submit or an extension. The timestamped email is the student's record that they tried. The instructor decides the rest.
Do professors have to give an extension when the LMS goes down?
That depends on the campus and the instructor. Some campuses have written guidance for outages near deadlines; many leave it to faculty. Students should ask, not assume, and campuses without guidance should consider writing a short version.
How can a university prepare for an LMS outage?
Write answers to the questions students ask during one: whether it's down for everyone, how to submit, whether extensions are possible, where the syllabus lives outside the LMS and how to reach the help desk after hours. Ask faculty to share the syllabus as a PDF in week one and to announce outages by email.
Can Journey give students an extension or contact professors?
No. Journey helps the student ask for an extension clearly and get started on the work, and it answers campus questions from the resource base gathered at setup. Extensions are the professor's decision.
