67f4ec27ab97d5ac7e2ad527e93b3e27daeb3edb
A workout deleted on Garmin's side after being linked to an activity 404s forever on get_workout_by_id, and today's fillPendingWorkouts retries it every sync indefinitely with no user-visible feedback -- just a perpetual "1 more workout pending" nudge. Distinguishes a definitive 404 (via garminconnect's own GarminConnectNotFoundError) from a transient failure, and stops retrying the former. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Description
No description provided
Languages
Go
72.8%
TypeScript
20.3%
Python
4.7%
CSS
2.1%