Use the same observation fields each time
Record the date, the normal task in progress, what happened, the exact display message, and whether normal operation later returned. Use plain descriptions. “Stopped during rinse; display blank; normal program unavailable” is easier for a provider to interpret than “the electronics are failing again.”
Show repeated and different behavior
Show the history to the service provider without claiming to know the cause. If the fault changes or becomes more serious, report the new condition directly rather than waiting for the next planned entry. Recording observations does not require opening equipment or attempting a repair.
Two entries may reveal that the fault occurs under different circumstances. If one event happened at startup and another halfway through a cycle, keep them distinct rather than forcing both into the same diagnosis. Link photos only when they were taken normally and show the relevant issue without unrelated personal details.
Know when the log has done its job
Share the observations with the appropriate provider and ask what information, if any, they need next. Do not repeat a potentially unsafe operation merely to collect another occurrence. If the condition changes or becomes urgent, use the relevant urgent contact route instead of waiting to build a more complete history.