Affiliate links on Android Authority may earn us a commission. Learn more.
Garmin CIRQA users say the fitness tracker is losing their workouts
Sep 18, 2026 — 11:41 AM ET

- Garmin CIRQA owners are reporting missing workouts.
- Starting a workout directly from the CIRQA band and tapping “End” from the Connect app results in the activity not being saved.
- Garmin is investigating the issue and has offered a temporary workaround that involves tapping “Resume” first and then stopping and saving the workout from the activity-recording screen.
There’s not much that’s more deflating than putting in a good workout and your fitness tracker not saving it. Unfortunately, this is the reality for some Garmin CIRQA users. The company’s Fitbit Air rival is losing activity data, but there is a workaround.
Owners of the Garmin CIRQA smart band are encountering a very particular issue that’s resulting in activities not being saved. According to the reports on Garmin’s forums (h/t: Gadgets and Wearables), the issue is caused by starting a workout directly from the band and ending it from the Connect app. Specifically, it happens when a user starts an activity by pressing the button on their CIRQA and taps “End” in Garmin Connect’s “Activity in Progress” prompt.
Garmin has acknowledged the reports and shared the feedback internally. The company says that it is currently investigating the glitch. It is also reaching out to some of the users in the thread to gather more information.

In the meantime, Garmin has offered a band-aid solution you can use until the bug is resolved. The next time you start a workout directly from the fitness tracker and you see the “Activity in Progress” prompt in the Connect app, select “Resume” instead of “End.” Hitting Resume will open the activity recording screen, where you can safely stop and save your activity.
This hasn’t been the only bug the CIRQA has recently faced. Back in late August, users reported that Bluetooth heart rate broadcasting was broken. However, the company has since rolled out an update that fixed this issue.
Thank you for being part of our community. Read our Comment Policy before posting.