Short answer: Repeated scans can come from the trigger, capture service, application handler or a retried transaction. Locate where the second event first appears before changing a timeout. A repeated barcode value can also represent a legitimate second unit, so equal values are not always duplicates.
Define when a repeat is valid
Write the required event sequence before selecting settings. Opening the same tote twice may be an error; counting two units with the same product code may be correct. A location code may be required again for the next task.
Identify the active record, the captured value, the business condition that permits another equal value and the point where the transaction is committed. Keep quantity and serial rules explicit so a simple value filter does not discard valid work.
Trace four checkpoints
Record the physical trigger action, capture-service output, application decision and stored transaction. Add timestamps, profile identity, device build and application version. Two stored records alone do not show which stage duplicated the action.
If one trigger produces two capture events, inspect the documented capture mode. If one event reaches the app but two records are stored, inspect application or service retries. Keep a decode sound separate from a received event and from the server’s acceptance.
Use capture controls for capture behavior
Where supported, a same-symbol timeout can suppress rapid repeated decodes. Other settings may delay different symbols or scanning activity. Their meaning depends on the scanner, capture service and active mode; a similar setting name is not enough to assume equivalent behavior.
Test both an accidental repeat and an intentional repeat. A long suppression interval can hide valid work, while a short one can allow an accidental second event. A scanner timeout cannot resolve an uncertain server submission or act as the application’s transaction identity.
Run a repeated-value test
Use a controlled tote T-204 and product P-771. Test a short press, a held trigger, two intentional unit scans and a retry after missing confirmation. Compare physical actions, delivered events, visible decisions and committed transaction IDs for each case.
Confirm that valid repeated units remain countable and that accidental actions do not create extra accepted work. Preserve the profile, labels, permitted-repeat rule and timestamps. Send that record through Contact; Integration & Support explains who owns capture configuration and application transaction rules.
Device options for this task
Compare AIDC GO HX-21 and AIDC GO HX-24 as Android PDA Barcode Scanners. Request the continuous-reading and output controls available on the exact scanner and software configuration.
Devices for this workflow
