How DataBuffer Keeps Your Workout Safe Offline

Basement gyms, garage setups, commercial gyms with concrete walls and crowded Bluetooth spectrums. The places where serious training happens are often the worst environments for wireless connectivity. And if your workout tracking depends on a constant Bluetooth connection, those environments become a problem.

Rack’s real-time BLE sync between your Garmin watch and iPhone is the core of the experience. But Bluetooth isn’t perfect. Connections drop. Signals degrade. And when they do, your workout data shouldn’t disappear with them. That’s what DataBuffer solves: complete data reliability regardless of connection quality.

The Problem: BLE Disconnection

Bluetooth Low Energy operates at 2.4 GHz, the same frequency band as Wi-Fi, microwave ovens, and dozens of other wireless devices in any commercial gym. Add concrete walls, metal equipment, and the simple physics of your body blocking the signal between your wrist and your phone in a gym bag, and you have a recipe for intermittent disconnections.

The failure modes are predictable:

• Distance drops. You leave your phone on a bench and walk to the cable station across the gym. Beyond ten to fifteen meters with obstacles, BLE signal strength drops below the connection threshold. The link dies.
• Interference spikes. Twenty people in a crowded gym with smartwatches, wireless earbuds, and Bluetooth-connected cardio equipment. The 2.4 GHz band gets saturated, and your connection becomes unreliable.
• Physical obstruction. Basement gyms with thick concrete walls between your phone charger and your squat rack. Garage gyms where your phone is inside and you’re training outside. Any scenario where a physical barrier sits between the two devices.
• iOS background limits. If your phone screen locks and iOS suspends the Rack app after several minutes in the background, the BLE connection may be interrupted until you open the app again.

Without a buffer system, any of these scenarios means lost data. Sets logged on the watch during a disconnection would simply vanish. For a tracking app that promises real-time sync, losing data when the connection drops would undermine the entire value proposition.

How DataBuffer Works

DataBuffer is a circular buffer implementation running on the Garmin watch in Monkey C. When the BLE connection to your iPhone is active, set data transmits immediately and the buffer stays empty. When the connection drops, DataBuffer activates automatically and begins storing every set locally on the watch.

The process is transparent. You keep training. You log sets on the watch exactly as you normally would. The watch UI doesn’t change. There’s no error message or interruption. The only indication that you’re in buffered mode is a small status indicator on the watch face showing the connection state.

Each set in the buffer includes the complete data packet: exercise identifier, rep count, weight, rest time since the previous set, heart rate zone at set completion, and a precise timestamp. Nothing is compressed or simplified. The buffer holds the same data that would have been transmitted in real time.

The circular buffer architecture means that the most recent sets always take priority. In the extremely unlikely scenario where you train for hours without a connection and the buffer fills, the oldest entries are overwritten first. In practice, the buffer capacity far exceeds what any normal session requires. Even a two-hour session with thirty or more sets sits comfortably within the buffer limits.

What Gets Buffered

Every data point that would normally transmit in real time is captured by DataBuffer when the connection is unavailable. The fidelity is identical.

• Exercise identification. The specific exercise you logged, mapped to Rack’s exercise database. Whether it’s a barbell bench press, a dumbbell lateral raise, or a cable row, the exercise ID travels with the set.
• Reps and weight. Exactly what you entered on the watch. No rounding, no approximation. If you logged 8 reps at 225 pounds, that’s what the buffer stores.
• Rest time. The interval between set completion and the start of your next set. This is calculated from timestamps, so even if the connection drops mid-rest, the timing is accurate.
• Heart rate zone. The HR zone captured from the watch sensor at the moment you complete each set. This biometric data is what enables verified PRs and per-set HR zone analysis.
• Timestamps. Each set carries a precise timestamp from the watch’s internal clock. This ensures that when the buffer replays, every set appears at the correct point in your workout timeline.

The result is full fidelity. A session where the connection dropped for fifteen minutes looks identical to a session where the connection was stable the entire time. You cannot tell the difference in your workout history.

Reconnection and Sync

When BLE reconnects, DataBuffer initiates a replay sequence. The buffered sets transmit to your iPhone in chronological order, exactly as they were recorded. The Rack iOS app receives each set, reconciles the timestamps against the workout timeline, and inserts them in the correct position.

The reconciliation process handles edge cases automatically. If you logged a set on your phone during the disconnection period (maybe a training partner was using your phone to track their own sets), the timestamps prevent conflicts. Watch data and phone data merge cleanly based on temporal ordering.

PR detection also runs during replay. If a buffered set represents a personal record, the app detects and records it with the same verification data as a real-time set. The timestamp, HR zone, and device confirmation are all present in the buffer. Verification doesn’t require a live connection at the moment of the lift. It requires that the watch was recording when the lift happened.

After replay completes, the buffer clears. The watch returns to real-time sync mode. The entire process typically takes a few seconds, depending on how many sets were buffered. For a typical disconnection of five to ten minutes with three to five sets logged, the replay is nearly instantaneous.

Train anywhere. Your connection is transparent. If it’s there, great. If it drops, DataBuffer has you covered. Your data is always safe.