Overview
Use this guide when you see Duplicate result for this schedule slot, or when two Results appear to cover the same scheduled inspection. Compare the records before you decide whether to keep both or invalidate one.
At a glance |
|
Who can do this | Super Users and Users with Result access; invalidation requires Super User access or Results › Delete. |
Where | Results |
Works on | Backend (web) |
Availability | All organizations |
Review the Results
1. Show the Id column
Open Results. At the top right of the table, click the cog labeled Setup visible columns. Select Id. The duplicate icon is inside that column, so hiding the column also hides the icon.
You can only compare Results you have permission to view. Schedule Reviewer access, or visibility as an Assignee or Performing User, does not automatically grant permission to invalidate Results. See Viewing Checklist Results for the visibility rules.
2. Compare the scheduled work
Filter to the relevant time range, Checklist, Schedule, and Location. Include the Asset filter when applicable. Show Schedule Start, Schedule Due, and Schedule End through the same column menu to compare the occurrence.
Check the actual Checklist, Schedule, Location, and Asset, rather than names alone. Separate slots can overlap. If the rows look the same but you cannot establish which occurrence they belong to, keep both Result IDs and ask Mobaro Support to check.
3. Compare times and reports
Show Answered, Received, and User(s). Answered is the completion time; Received is when Mobaro received the Result. A Result answered earlier can arrive later and receive the duplicate marker. The time difference alone does not prove the device was offline.
Select each Result and click View. Review the answers, comments, attachments, and any associated Assignments. Ask the Users which work each record represents. Do not choose a Result to keep only because it arrived first or has a better score.
4. Decide whether to keep both
Keep both Results if both are valid records of work. If one is an accidental submission that should not count in reporting, have an authorized User review it for invalidation. Record why it is surplus and which Result should remain.
🛑 Critical: Before using Invalidate, confirm which Result represents the required work and whether that work meets your operating requirements. A completed slot is not proof that a safety check passed or was approved.
If you invalidate a Result
A Super User or a User with Results › Delete can use Invalidate. Follow Invalidating Results for the dialog and permissions, with these duplicate-specific effects in mind:
Invalidating only the duplicate: removes that Result from the slot’s duplicate list. The existing completion entry remains.
Invalidating the Result counted for the slot: Mobaro looks for a matching duplicate and promotes one to the completion entry. Among eligible duplicates, it chooses the earliest Answered time. The promoted Result stops being marked as a duplicate.
No eligible replacement: the slot can become incomplete. An expired occurrence can appear as missing when no completion remains for required work. Do not assume another visible Result is an eligible replacement.
For promotion, Mobaro matches the Checklist and Location, and also the Asset when the slot is Asset-targeted. After invalidation, refresh Results and check the remaining Result, the slot, and any approval requirements.
Read the dialog options before confirming. Make the active invalidated results resumable is selected by default. For expired Results, Reschedule the expired results is selected by default when you have permission to reschedule. Rescheduling can create a new Ad Hoc Slot.
If the purpose is only to remove an accidental extra Result and no redo is required, clear the applicable resume or reschedule option. Do not accept those defaults automatically. Invalidation keeps the answers, but removes that completion from normal reporting; depending on the options, the record becomes resumable or appears under Invalidated Results.
Reduce repeated submissions
Agree who owns each scheduled inspection, especially when several Users or devices can perform it.
Sync devices before checking available work. Save unfinished work to the cloud before another User continues it, and confirm the shared progress is available.
When continuing work, use the intended saved Result rather than starting a new copy. A second device may not know about progress that exists only on the first device.
If duplicates recur, contact Mobaro Support through Help in the Backend or [email protected]. Include both Result IDs, the Checklist and Schedule, the Location and Asset, the slot times and time zone, and the Answered and Received times. Describe whether multiple devices, offline work, or resumable work were involved. See Contact Information.
Frequently asked questions
Can I disapprove a duplicate instead of invalidating it?
Disapproving a Result records a review decision. It does not remove the duplicate from the slot or automatically exclude it from reporting. Use invalidation only if the Result should not count at all. See Disapproving Results.
The app should prevent duplicates. Why did two Users start the same Checklist?
A second device may not see progress that has not been saved to the cloud and synchronized. The duplicate marker cannot establish the cause. Ask Mobaro Support to review the device and Result details if repeated starts continue after the team confirms shared progress.
Should I invalidate both Results and start again?
Do not invalidate both just to clear the marker. First establish which records are valid and whether required work is complete. Removing both can leave no eligible completion for the slot. Ask your reviewer or Mobaro Support when the correct record is unclear.