← Back to Help Center
Cantaloupe Support

MoMa not syncing data

Fix sync delays, stale sales logs, and device offline status.

Updated Feb 9, 2026

Overview

Confirm the device shows online and the SIM is active. Check the last sync timestamp in MoMa and attempt a manual sync.

If data stays stale, reboot the reader and confirm the machine profile and location assignment are correct. Sync issues often occur when a reader is assigned to the wrong site or machine.

Update firmware if available and verify cellular signal strength at the cabinet.

Portal checks

  • Verify the device is mapped to the correct location and machine.
  • Check for data import errors or status warnings.
  • Review the last successful transaction timestamp.

Device actions

  • Power cycle the reader and confirm it reconnects.
  • Reseat the SIM and verify antenna placement.
  • Test a small transaction to force a sync.

Escalation info

  • Provide device ID, location ID, and last sync time.
  • Note signal strength and cabinet placement.
  • Attach screenshots of MoMa error messages.

Expanded guidance

  • Confirm all steps are documented so the next technician can reproduce the results.
  • Capture before/after metrics (errors cleared, sales restored, or uptime improved).
  • Review machine, reader, or route settings to ensure they match location standards.

Common pitfalls

  • Skipping a controlled test leads to false positives.
  • Updating hardware without documenting configuration changes.
  • Forgetting to verify payout, refund, or reconciliation data after changes.

Next-step checklist

  • Run a final test with known-good inputs.
  • Log the outcome with date, time, and device identifiers.
  • Schedule a follow-up check if the location has high traffic or seasonal demand.

<!-- expanded:v2 -->

Additional details

Operational notes

  • Document changes with time, machine ID, and location name.
  • Verify settings, pricing, and service modes after each fix.
  • Capture before/after results to confirm resolution.

Field checklist

  • Test with known-good inputs and controlled conditions.
  • Validate telemetry, alerts, and payment logs where applicable.
  • Confirm location expectations and update the site contact.

Common root causes

  • Configuration drift after firmware or component swaps.
  • Inconsistent power or network conditions at the location.
  • Gaps in preventive maintenance routines.

Next steps

  • Monitor for 7 days and note any repeat errors.
  • Schedule follow-up if the site is high-traffic.
  • Escalate with full logs and photos if issues repeat.

Cantaloupe specifics

Device pairing

  • Verify the reader is paired to the correct machine ID.
  • Confirm MoMa configuration and device firmware are current.

Alerts

  • Ensure alert thresholds align to route service windows.
momasyncdata