Past Continuous for Interrupted Production Work

By the end of this lesson, you will be able to...

• use past continuous to show an action that was in progress at a past moment.

• combine past continuous with past simple in an incident timeline.

• explain whether a sentence describes background work or the event that interrupted it.

Idea in one sentence: Past continuous shows what was already happening when another past event changed the situation.

Core Insight

In the previous lesson, past simple made finished events visible:

We deployed the fix at 09:30.
The worker restarted after the deploy.
The alert cleared five minutes later.

Past simple is good for points on a timeline.

But sometimes a timeline also needs a line, not only points.

Consider this sentence:

The job was retrying when the node restarted.

The job was retrying is not a finished point. It is background work that was in progress.

the node restarted is the event that interrupted or changed that background work.

That is the core job of past continuous in technical English:

was/were + -ing

It shows an action that was happening around a past moment.

Past continuous is especially useful in production work because incidents often involve overlapping events. A job is retrying. A deploy is running. A migration is copying rows. Then another event happens and changes the story.

The Small Situation

Imagine a worker processing jobs from a queue.

At 10:00, one job fails. At 10:01, the worker starts retrying it. At 10:02, the node restarts. At 10:03, the job appears again in the queue.

You could write:

The job retried. The node restarted.

Those two past simple sentences are not wrong, but they are thin.

They hide an important relation: the retry was already in progress when the restart happened.

This is clearer:

The job was retrying when the node restarted.

Now the reader sees two layers:

• background action: The job was retrying
• interrupting event: the node restarted

The sentence does not say the restart caused the retry. It says the retry was in progress at the moment of the restart.

That distinction matters. A production timeline should not invent causality. It should show timing first.

Plain to Precise

Plain meaning:

Use past continuous when you want to say, "This action was happening then."

In this scenario:

The job started retrying before the node restart. The retry was still in progress when the restart happened.

Technical name:

This is past continuous:

subject + was/were + verb-ing

Examples:

The job was retrying.
The worker was draining the queue.
We were checking the logs.
The migration was copying rows.
The deploy was rolling out to one region.

Use was with one thing:

The job was retrying.
The worker was restarting.

Use were with we, they, or many things:

We were checking the logs.
The replicas were catching up.

Then add the past simple event that happened during that action:

The job was retrying when the node restarted.
We were checking the logs when the alert cleared.
The migration was copying rows when the lock timeout fired.

The Naive Idea

A common naive idea is:

Use past simple for everything that happened in the past.

That worked well in the previous lesson when each sentence named a finished event:

We found the config error.
We rolled back the deploy.
Error rate returned to normal.

But past simple can make overlapping actions look like separate dots:

The migration copied rows. The lock timeout fired.

That sentence pair does not show whether the copy finished before the timeout, started after the timeout, or was still happening when the timeout fired.

Past continuous makes the overlap visible:

The migration was copying rows when the lock timeout fired.

Now the reader can see the background action and the interrupting event.

A Worked Timeline

Start with this rough production note:

10:00 deploy started / 10:01 worker draining queue / 10:02 node restarted / 10:03 job appeared again / 10:04 alert fired

The note has events, but the overlap is hidden.

Step 1: mark points and background actions.

Step 2: write the simple event sequence.

The deploy started at 10:00.
The node restarted at 10:02.
The job appeared again at 10:03.
The alert fired at 10:04.

That sequence is clear, but it misses what the worker was doing during the restart.

Step 3: add the background action.

The worker was draining the queue when the node restarted at 10:02.

Step 4: combine the update.

The deploy started at 10:00. The worker was draining the queue when the node restarted at 10:02. The job appeared again at 10:03, and the alert fired at 10:04.

Now the timeline has both kinds of information:

• finished points: started, restarted, appeared, fired
• background action: was draining

Naive failure contrast:

The worker drained the queue when the node restarted.

That version sounds like the worker completed the drain at the moment the node restarted. It may even sound like the restart caused the drain to finish.

If the drain was only in progress, use past continuous:

The worker was draining the queue when the node restarted.

What When Does

The word when often connects past continuous and past simple.

The job was retrying when the node restarted.

The structure is:

background action + when + interrupting event

But you can reverse the order:

When the node restarted, the job was retrying.

Both sentences are correct.

The first order emphasizes the background action first. The second order emphasizes the interrupting event first.

In incident writing, choose the order that helps the reader answer the next question.

If the reader asks, "What was the job doing?", start with the job:

The job was retrying when the node restarted.

If the reader asks, "What happened during the restart?", start with the restart:

When the node restarted, the job was retrying.

Do not overuse long when sentences. If a sentence becomes heavy, split it:

The node restarted at 10:02. At that moment, the worker was draining the queue.

That split is often easier to scan in an incident report.

Choosing Between Past Simple and Past Continuous

When you write an incident timeline, use this decision table.

The difference is small, but it changes the reader's model.

Compare:

The migration copied rows when the timeout fired.
The migration was copying rows when the timeout fired.

The first sentence can sound as if the copy happened as one finished event. The second sentence makes the ongoing action visible.

Now compare:

The worker was restarting at 10:02.
The worker restarted at 10:02.

The first sentence says the restart was in progress at 10:02. The second sentence says the restart happened at 10:02.

In production writing, this difference can affect what the reader checks next. If the restart was still in progress, the reader may wait for completion. If the restart already happened, the reader may look for effects after the restart.

Negative and Still-In-Progress Sentences

Past continuous also helps when something had not finished yet.

The migration was still copying rows when the timeout fired.
The worker was not processing new jobs when the alert fired.
We were not changing production when the error rate increased.

The word still is useful when the duration matters:

The queue was still draining at 10:15.

That sentence tells the reader that the action continued longer than expected.

The negative form uses was not or were not:

The worker was not processing jobs.
We were not deploying a new version.
The replicas were not catching up.

This can prevent a false assumption.

Imagine someone asks, "Did the deploy cause the spike?"

A careful answer might be:

We were not deploying when the error rate increased. The deploy had finished ten minutes earlier.

That answer separates background activity from a finished event. It does not solve the incident, but it removes one bad theory from the timeline.

So far, the useful model is:

past simple = event point
past continuous = action in progress
when = the moment where the two meet

You can use that model before you know the full root cause. First make the timeline honest. Then make the cause claim only when the evidence is strong enough. This order keeps the English useful during investigation, not only after everyone already knows the answer. It also helps teammates correct one piece of the story without rewriting the whole update. That makes the timeline easier to maintain as new evidence arrives and old guesses are removed.

Past Continuous Does Not Prove Cause

Past continuous is good at showing overlap.

It is not proof of cause.

This sentence is careful:

The job was retrying when the node restarted.

It says the retry and the restart overlapped.

This sentence is stronger:

The node restart caused the job to retry.

Only write that stronger sentence when you have evidence.

The trade-off is useful: past continuous lets you report timing before you fully know cause. That keeps the update honest. The cost is that the reader may still ask, "Did the restart cause the retry?" If you do not know yet, say so:

The job was retrying when the node restarted. We do not know yet whether the restart caused the duplicate job.

That is better than hiding uncertainty inside confident grammar.

Common Confusions

Confusion: Past continuous means the action finished

Why it is tempting:

The sentence is about the past, so it feels complete.

Better model:

Past continuous says the action was in progress at a past moment. It does not say whether the action finished.

The migration was copying rows when the timeout fired.

Maybe the migration later finished. Maybe it failed. The sentence only shows what was happening at the moment of the timeout.

Confusion: Past continuous explains the root cause

Why it is tempting:

When two events appear in one sentence, the reader may feel a cause relation.

Better model:

Past continuous shows overlap. Add cause only when evidence supports it.

The worker was draining the queue when the node restarted.

This is timing.

The node restart interrupted the drain.

This is a cause claim.

Confusion: Past simple and past continuous are style choices

Why it is tempting:

Both forms can describe past production work.

Better model:

They answer different questions.

Past simple answers:

What happened?

Past continuous answers:

What was happening then?

Use the question that matches the reader's need.

Check Your Understanding

Check: Which sentence best shows an action in progress during a restart?

A. The job retried when the node restarted. B. The job was retrying when the node restarted. C. The job retries when the node restarts.

Think first, then reveal.

Answer: B. was retrying shows the background action in progress. restarted is the past simple event.

Check: Which sentence is careful about cause?

A. The job was retrying when the node restarted. B. The node restart caused the retry. C. The node restart definitely caused all queue behavior.

Think first, then reveal.

Answer: A. It reports timing without claiming cause. B may be correct only if evidence supports it.

Practice

Revise this rough note:

10:00 deploy started / worker draining queue / 10:02 node restarted / job appeared again / alert fired

Model answer:

The deploy started at 10:00. The worker was draining the queue when the node restarted at 10:02. The job appeared again, and the alert fired at 10:04.

Why it works:

• started, restarted, appeared, and fired are finished events.
• was draining shows background work in progress.
• The sentence does not claim that the restart caused the duplicate job.

Now write a second version where you want to emphasize the restart:

When the node restarted at 10:02, the worker was draining the queue. The job appeared again one minute later.

Both versions are useful. Choose the one that answers the reader's current question.

Daily Practice Lines

Say or write these lines during the day:

The job was retrying when the node restarted.
The worker was draining the queue when the alert fired.
We were checking the logs when the error rate dropped.

Keep one line from the previous lesson:

We deployed the fix at 09:30.

Change one technical noun:

job -> migration -> worker -> deploy -> alert

Keep asking: is this a finished event, or was it happening when another event occurred?

Resources

• [ARTICLE] Cambridge Dictionary Grammar: Past continuous
  • Link: https://dictionary.cambridge.org/grammar/british-grammar/past-continuous-i-was-working
  • Focus: Review the form was/were + -ing and its use for actions in progress in the past.
• [ARTICLE] Cambridge Dictionary Grammar: Past simple
  • Link: https://dictionary.cambridge.org/grammar/british-grammar/past-simple-i-worked
  • Focus: Compare timeline points with background actions.
• [REFERENCE] Microsoft Writing Style Guide: Be clear and concise
  • Link: https://learn.microsoft.com/en-us/style-guide/welcome/
  • Focus: Keep incident timelines readable and direct.

Key Takeaways

• Use past continuous for an action that was in progress at a past moment.
• Use past simple for the event that interrupted or changed that action.
• Past continuous shows overlap; it does not prove cause.
• Split long timeline sentences when the reader needs a clearer sequence.