How to explain a problem that only happens sometimes in English

Name the part or action you can observe. "My computer is broken" could mean many things. "The screen goes black, but I can still hear the video" gives the listener a clearer starting point.

You can build a short report from an action and an interruption:

• "The mouse pointer moves normally, then stops responding."
• "The app opens, but sometimes it closes before the document appears."
• "The printer starts a page, then stops halfway through."
• "The sound disappears for a few seconds and then comes back."

Use only details you actually noticed. A screen going black does not, by itself, prove that the whole computer turned off. If you do not know, say: "I can't tell whether the computer is still running."

For an interrupted conversation happening right now, the video-call audio guide helps you agree how to continue. Reporting a recurring fault is a different task: your listener needs an account of what happened across separate occasions.

"Sometimes it stops" reports an occasional event. "It keeps stopping" draws attention to repeated stops. Neither sentence tells the listener exactly how many times it happened.

"Intermittent" is the adjective you may see in a support form or hear from a technician. Collins defines intermittent as something that occurs with interruptions rather than continuously. You can say "an intermittent problem" or "It works intermittently."

You do not need that word to explain yourself. "It works for a while, stops, and then works again" may be easier to say and understand.

Be careful with "always" and "never." If a device worked this afternoon after failing in the morning, "It never works" contradicts your own account. Try "It isn't reliable" followed by the specific examples you remember.

Avoid learning frequency words as fixed percentages. The British Council's frequency lesson explains common word positions and count-plus-time expressions. Its teaching team also notes that words such as "sometimes" and "often" do not correspond to fixed numbers.

When you have a real count, give it: "It stopped three times during a twenty-minute call." If you did not count, say "several times" or "I don't remember exactly."

"Three times" answers how many events occurred. "For three minutes" describes how long something lasted. A support agent may need both.

What you mean	A clear example
Number of failures	It stopped twice this morning.
Length of one failure	The second interruption lasted about a minute.
Time before a failure	It worked for ten minutes before stopping.
When you first noticed it	I first noticed it yesterday afternoon.
Current condition	It's working at the moment.

"It stops every ten minutes" suggests a repeating interval. Do not use it simply because one stop happened after ten minutes. If the intervals vary, say: "Sometimes it stops after a few minutes; other times it runs much longer."

You can mark an estimate without apologising: "About a minute, though I wasn't timing it." That gives useful information without pretending you used a stopwatch.

Compare these two reports:

"The update broke the app."

"I first noticed the problem after the update. I don't know whether they're connected."

The second reports a sequence and leaves the cause open. Use it when you know the order of events but have not established an explanation.

You can also describe a possible condition: "So far, I've only noticed it when opening large files." The words "so far" matter if you have not tested every situation.

If asked whether something happens on another device, an honest answer might be "I haven't checked that." This is different from "It doesn't happen on another device," which reports a result.

Write down an error message exactly if you can. If you only remember part of it, say "I remember the word connection, but not the full message." Do not invent an error code to make the report sound technical.

A device may work while you are speaking to support. Acknowledge that observation while preserving the earlier history:

"Yes, it's working now. The issue comes and goes. It stopped twice earlier today."

Then ask how to document another occurrence: "If it happens again, what details would help you?"

If someone asks you to reproduce the problem, they mean making the same problem happen again under similar conditions. You can answer: "I can't make it happen on demand. These are the steps I was taking when I noticed it."

Ask for an explanation if the proposed next step is unclear. The English clarification practice guide covers checking an instruction before acting on it. This article does not recommend repeatedly triggering a fault or changing settings without understanding the instructions.

Use this fictional log. Read it once, then explain the problem without reading every row aloud.

Time	Observation
09:00	The printer completed a two-page document.
09:15	It stopped halfway through a different document.
09:40	It completed a one-page document.
10:05	It stopped halfway through another document.
10:20	It completed the page used for a demonstration.

Your partner asks: "Is it working now? Has it happened more than once? Does it always fail on long documents?"

A possible response is: "It completed the demonstration page, but it stopped twice earlier this morning. I don't have enough information to say whether the document length matters."

Check that your answer preserves both successful and failed attempts. The log does not give the length of every document, explain the cause, or establish how long either interruption lasted. Leave those details unknown.

For a second round, your partner changes one successful attempt into a failure. Give a fresh report with the new count. The exercise is complete when your listener can distinguish what happened, what is happening now and what remains untested.