AmaraBell0687 · 15 Dec 2025, 12:30 UTC
Tell support directly which part was a later reconstruction and retain the original occurrence's message, history and operator account separately. The staged pause may explain the position, but it cannot establish the cause or timing of the original stop.
18 pointsI've corrected the description. Embarrassing, but yes, we filmed the position later. Original message wasn't saved.
11 pointsIs any original event history still available? Check that before arranging more filming. The useful next evidence may be in a retained record rather than another view of the arm.
20 pointsI've sent a reconstruction too, but labelled it separately. Useful for showing a cramped contact; useless for proving which signal changed during the real occurrence.
4 pointsController history retained. PLC lead-in isn't. Technician is checking what the original controller entries actually identify.
17 pointsDid the operator stop it deliberately at the same point as the earlier event, or just somewhere nearby? Even the position explanation could be misleading if support assumes a precise match you didn't intend.
14 pointsKeep that uncertainty with the reconstructed clip, Amara. It may remain useful context, but do not let a carefully chosen camera angle turn it into a substitute occurrence.
17 pointsNearby, not exact. I've said that too. The real stop and the later filming now have separate entries.
7 pointsWho can preserve the next real occurrence before its history rolls over? The current reconstruction problem should not leave both shifts without a usable capture method.
8 pointsMaya's right. A short capture list is cheaper than another afternoon arguing about what a video was meant to show.
24 pointsThomas, did support still use your labelled reconstruction? I'm asking because ours sometimes asks for a clearer picture when it really needs an earlier event, and people end up filming the wrong thing very clearly.
3 pointsYes, to understand the physical access. The actual diagnostic answer used the captured event history. We kept both, with different jobs to do.
9 pointsBoth shift technicians now have support's capture list. Thanks Maya. Original controller entries don't identify the missing receiving condition.
16 pointsThen leave that old condition unknown and capture the required source states around a new occurrence, with its exact message, job version and sleeve fixture identity. The reconstruction can remain clearly marked background.
16 pointsHas support stated which source states it needs, rather than only asking for a longer video?
4 pointsYes. Controls and support agreed the specific export. No new occurrence captured yet.
15 pointsThat's a clearer next step. I'd put the reconstruction label on the clip itself as well as the ticket description, because attachments have a habit of travelling without the sentence that explains them.
18 pointsKeep the exact original and the labelled teaching copy distinguishable if you do that. The aim is to prevent misreading, not overwrite the material explaining how the ticket became confused.
22 pointsThis discussion is closed to new replies after six months without activity. Last activity: .