Response code/exception "0"

[Spyros]

Hello, 

Lately, our subscriber endpoint stats show a response code/exception of "zero" (see below). 

Can you please let me know that this code stands for? We are trying to figure out whether the error is on the Fitbit server side or our application/server side

Thank you, 

Spyros 

[JohnFitbit]

Hi @Spyros,

Can you PM me your Client ID so I can take a look at our logs? 

Hope to hear from you soon!

[Spyros]

I just PM you.

[JohnFitbit]

Hi @Spyros,

The response code/exception "0" are you seeing occurs when your application doesn't respond to a subscription notification with a 204 No Content within a few seconds of receiving the alert. 

For more information, see our documentation for Responding to a notification.

I hope this helps. Let me know if you have any additional questions.

[Spyros]

Thank you John. Our application is programmed so that it returns a 204 No content notification. Could these errors be due to a network issue or server issue on your side? We've noticed in our log files a bunch of Gateway errors (e.g. bad gateway or gateway timeout). 

[JohnFitbit]

@Spyros Its possible, but I can't say for sure yet. The next time you see the response code '0', could you provide me with the timestamp it occurred as well as any error that you received from it? I can take a look on our end to see if it's anything on our side.

Hope to hear from you soon!

[skitsiou]

@JohnFitbit I looked into our log files and noticed that we don't have any messages/error codes associated with the "0" response/exceptions shown in the subscription endpoint stats table. Is it possible for you to look at your system logs and see what's happening at the hours shown in the table below?

Time Response Code/Exception Delivery Time(ms) Messages Payload Size(bytes)

241.

2019-10-09 01:26:45:000 +0000

0

0

1

117

237.	2019-10-09 01:27:42:000 +0000	0	0	1	117
238.	2019-10-09 01:27:34:000 +0000	0	0	1	117

243.

2019-10-09 01:25:52:000 +0000

0

0

1

117

246.

2019-10-09 01:25:12:000 +0000

0

0

1

117

252.

2019-10-09 01:24:09:000 +0000

0

0

1

117

254.

2019-10-09 01:23:56:000 +0000

0

0

1

117

256.

2019-10-09 01:23:41:000 +0000

0

0

1

117

[JohnFitbit]

Hi @skitsiou,

Welcome to the forums!

Could you please PM me your Client ID so I can take a look at our logs?

Hope to hear from you soon!

[Spyros]

John this is for the same application I emailed you before (Spyros). Sorry for the confusion, but the system was asking me to use a separate user name to post my message.

[JohnFitbit]

@Spyros Thanks for the clarification. I checked the timestamps of your recent examples and it looks like it lined up with a service interruption we had around that time frame. The issue was identified and a resolution was promptly put in place soon after.

If you continue to see these exceptions, feel free to let me know and I'll be happy to check on things from our end.