Error Codes & Troubleshooting

When something goes wrong, you may see one of these error codes or messages on your watchface. This page explains what each one means and how to fix it.

Quick Error Reference

Authentication Errors

Failed Authentication

Message: "Failed to authenticate" or "Auth Failed"

Cause: Your Dexcom Share credentials are incorrect or the wrong region is selected.

Solution:

  • Check your username and password by logging in on the Dexcom website for your region
  • Make sure you picked the right region (US, Outside US, or Japan)
  • If you log in with a phone number, include the country code (e.g., +11234567890)
  • Use your main Dexcom account, not a follower's login
  • Check that Dexcom Share is on, with at least one follower set up

Maximum Attempts Exceeded

Message: "Maximum authentication attempts exceeded"

Cause: Too many failed logins in a short time.

Solution:

  • Wait 30-60 minutes before trying again
  • Check your login details before you try again
  • Contact Dexcom support if it keeps happening

Session Errors

Session Not Found

Message: "Session ID not found"

Cause: Your session has expired or was never created.

Solution:

  • Wait 5-10 minutes. The app logs in again by itself
  • Enter your login details again in the app settings
  • Restart your watch if it keeps happening

Session Invalid or Timed Out

Message: "Session not active or timed out"

Cause: Your Dexcom Share session has expired (typically after 24 hours).

Solution:

  • This is normal. The app logs in again by itself
  • Wait 5-10 minutes for the next update
  • If the data doesn't come back, check your internet connection

Configuration Errors

Invalid Username

Message: "Username must be non-empty string"

Cause: No username in the settings.

Solution:

  • Open the Garmin Connect IQ app
  • Go to the CGM+ App settings
  • Enter your Dexcom Share username

Invalid Password

Message: "Password must be non-empty string"

Cause: No password in the settings.

Solution:

  • Open the Garmin Connect IQ app
  • Go to the CGM+ App settings
  • Enter your Dexcom Share password

Server Errors

No Current Glucose Reading Available

Message: "No current glucose reading available"

Cause: Dexcom sent no recent glucose data. This usually means:

  • You use a Follower account instead of your main Dexcom account. Followers can't get readings through the Share API
  • Dexcom Share is not enabled on your account
  • Dexcom has no recent sensor readings (e.g. sensor warm-up, signal loss, or sensor expired)

Solution:

  • Use your main Dexcom account credentials, not a follower's login
  • Open the Dexcom app and enable Share: go to Connections → Share and make sure sharing is on with at least one follower
  • Check that your sensor is active and your Dexcom app gets live readings
  • Just inserted a new sensor? Wait until the warm-up is done

Invalid or Malformed JSON

Message: "Invalid or malformed JSON in server response"

Cause: The Dexcom server sent an unexpected or broken response.

Solution:

  • This is usually temporary. Wait 5-10 minutes and try again
  • Check the server status of your CGM service
  • Let me know if it keeps happening

Unknown Error Code

Message: "Unknown error code in server response"

Cause: The Dexcom API sent an error code the app doesn't know.

Solution:

  • Check for an app update
  • Let me know, with the error code if one is shown

Unexpected Server Response

Message: "Unexpected server response"

Cause: The Dexcom server responded in an unexpected way.

Solution:

  • Wait 5-10 minutes
  • Check your internet connection
  • Check that the Dexcom services are up

Garmin Communications API Errors

These errors come from the Garmin Communications API, when the watch has network, Bluetooth or communication problems.

Click an error to jump to its fix:

General Errors

Unknown Error (0)

Code: UNKNOWN_ERROR

Cause: An unknown error.

Solution: Restart your watch and check the connection.

Bluetooth (BLE) Errors

Generic BLE Error (-1)

Code: BLE_ERROR

Cause: A general Bluetooth error.

Solution:

  • Restart Bluetooth on your phone
  • Make sure your watch is paired and connected
  • Move closer to your phone

BLE Host Timeout (-2)

Code: BLE_HOST_TIMEOUT

Cause: Timed out waiting for a response from the host (phone).

Solution:

  • Check that your phone is nearby and connected
  • Check that your phone's Bluetooth is on
  • Restart the Garmin Connect app

BLE Server Timeout (-3)

Code: BLE_SERVER_TIMEOUT

Cause: Timed out waiting for a response from a server.

Solution:

  • Check that your phone has internet
  • Wait 5 minutes. The app tries again by itself
  • Check that the Dexcom servers are up

BLE No Data (-4)

Code: BLE_NO_DATA

Cause: The response had no data.

Solution: Wait for the next update. Check that the Dexcom app has readings.

BLE Request Cancelled (-5)

Code: BLE_REQUEST_CANCELLED

Cause: The request was cancelled by the system.

Solution: This is normal. The app tries again by itself.

BLE Queue Full (-101)

Code: BLE_QUEUE_FULL

Cause: Too many requests have been made.

Solution:

  • Wait a few minutes for the queue to clear
  • Close other Connect IQ apps
  • Restart your watch if it keeps happening

BLE Request Too Large (-102)

Code: BLE_REQUEST_TOO_LARGE

Cause: The request data was too large.

Solution: Contact me. This is an app issue.

Unknown Send Error (-103)

Code: BLE_UNKNOWN_SEND_ERROR

Cause: Send failed for an unknown reason.

Solution:

  • Check the Bluetooth connection
  • Restart your watch and phone

BLE Connection Unavailable (-104)

Code: BLE_CONNECTION_UNAVAILABLE

Cause: No BLE connection is available.

Solution:

  • Make sure your phone's Bluetooth is on
  • Keep your phone within range (< 10 meters)
  • Re-pair watch with phone if needed

HTTP Request Errors

Invalid HTTP Header Fields (-200)

Code: INVALID_HTTP_HEADER_FIELDS_IN_REQUEST

Cause: The request had invalid HTTP header fields.

Solution: Contact me. This is an app configuration issue.

Invalid HTTP Body in Request (-201)

Code: INVALID_HTTP_BODY_IN_REQUEST

Cause: The request had an invalid HTTP body.

Solution: Contact me. This is an app issue.

Invalid HTTP Method (-202)

Code: INVALID_HTTP_METHOD_IN_REQUEST

Cause: The request used an invalid HTTP method.

Solution: Contact me. This is an app issue.

Network Timeout Errors

Network Request Timed Out (-300)

Code: NETWORK_REQUEST_TIMED_OUT

Cause: The request timed out before a response came in.

Solution:

  • Check that your phone has a stable internet connection
  • Try switching between WiFi and cellular data
  • Wait 5 minutes. The app tries again by itself
  • Check the server status of your CGM service

HTTP Response Errors

Invalid Response Body (-400)

Code: INVALID_HTTP_BODY_IN_NETWORK_RESPONSE

Cause: The response from the server could not be read.

Solution:

  • Wait 5 minutes. The app tries again by itself
  • Check your login details and CGM System in the settings
  • Check that your phone has a stable internet connection

Invalid Response Headers (-401)

Code: INVALID_HTTP_HEADER_FIELDS_IN_NETWORK_RESPONSE

Cause: The response from the server had invalid header fields.

Solution:

  • Wait 5 minutes. The app tries again by itself
  • Try switching between WiFi and cellular data

Response Too Large (-402)

Code: NETWORK_RESPONSE_TOO_LARGE

Cause: The response was too large for your watch.

Solution:

  • Wait 5 minutes. The app tries again by itself
  • With Nightscout Direct, switch to regular Nightscout, which sends less data

Out of Memory (-403)

Code: NETWORK_RESPONSE_OUT_OF_MEMORY

Cause: Your watch ran out of memory while reading the response.

Solution:

  • Wait 5 minutes. The app tries again by itself
  • Restart your watch
  • With Nightscout Direct, switch to regular Nightscout, which sends less data

Storage & Connection Errors

Storage Full (-1000)

Code: STORAGE_FULL

Cause: The watch storage is too full to store the response.

Solution:

  • Delete old activities/data from your watch
  • Remove unused apps or music
  • Sync your watch with Garmin Connect to free up space

Secure Connection Required (-1001)

Code: SECURE_CONNECTION_REQUIRED

Cause: The address must start with https://.

Solution:

  • With Nightscout, check that your URL starts with https://

Unsupported Response (-1002)

Code: UNSUPPORTED_CONTENT_TYPE_IN_RESPONSE

Cause: The server sent something the app did not expect, for example a web page instead of data.

Solution:

  • Check your URL or login details and CGM System in the settings
  • Wait 5 minutes. The app tries again by itself

Request Cancelled (-1003)

Code: REQUEST_CANCELLED

Cause: Your watch cancelled the request.

Solution:

  • Wait 5 minutes. The app tries again by itself

Connection Dropped (-1004)

Code: REQUEST_CONNECTION_DROPPED

Cause: The connection was lost before a response came in.

Solution:

  • Check that your phone is near your watch and connected
  • Check that your phone has a stable internet connection
  • Wait 5 minutes. The app tries again by itself

Display Messages

--- (Three Dashes)

Meaning: No data available or app not configured.

Solution:

  • Enter your CGM login in the app settings
  • Wait 5-10 minutes for the first data fetch
  • Check that your phone is connected and has internet

OLD (or timestamp > 10 minutes)

Meaning: The last reading is more than 10 minutes old.

Solution:

  • Check that your phone is connected to your watch
  • Check that your phone has internet
  • Make sure your CGM app is syncing
  • Wait for the next update (every 5 minutes)

General Troubleshooting

Common Solutions for Any Error:

  1. 1. Check the Connection
    • Make sure your phone's Bluetooth is on
    • Check that your phone has internet (WiFi or cellular)
    • Check that the Garmin Connect app is running
  2. 2. Check Dexcom Share (Dexcom only)
    • Open the Dexcom app and check that it gets readings
    • Check that Share is on, with at least one follower
    • Check that data syncs to the Dexcom cloud
  3. 3. Restart Services
    • Close and reopen the Garmin Connect app
    • Restart your watch
    • If needed, restart your phone
  4. 4. Update App
    • Check for CGM+ App updates in the Connect IQ Store
    • Make sure the Garmin Connect app is up to date

More help: See the FAQ or go back to the Introduction.

⚠️ Important Disclaimer

  • NOT FOR MEDICAL DECISIONS: This app is for informational purposes only and should NOT be used to make medical decisions.
  • Always verify readings: Confirm glucose values with your official CGM receiver or app before taking action.
  • Emergency situations: In case of extreme glucose levels or medical emergencies, use your primary CGM device.
  • Delayed data: Readings may be delayed by several minutes due to how often the app can sync.
  • No liability: The developer assumes no responsibility for health outcomes related to the use of this app.
  • Not affiliated: This app is not approved by, endorsed by, or affiliated with Dexcom, Abbott (Libre), or any other medical device company.