Delay between web-hook notification & datas availability ?

[Fred.A]

Hey, 

I use since a while a micro-api which listen for a web-hook and retrieve datas from API when new datas are available. 

The app : When i use my Aria 2 scale, i synchronize my BMI/ %fat and weight to my own tracker. Everything worked fine until this couple of past weeks. 

My configuration : 

- in dev-center, a registered app with this https://dev.fitbit.com/build/reference/web-api/developer-guide/using-subscriptions/

- success rate is enough to be triggered

Here is an example of data I received from fitbit as I record a new weight : 

new datas available [

{

collectionType: 'body',

date: 'yyyy-MM-dd',

ownerId: 'userId',

ownerType: 'user',

subscriptionId: '1'

}

]

Then, I use the "date" field to perform a request to API (with valid OAuth token) to 

let endpointUrl = `/body/log/weight/date/${date}.json`

It seems data take a while before being available. 

Until I noticed it, everything just worked fine, and I could request my datas, as soon as I received the notification.

For example, I use my scale this morning, and I tried the same request in the morning (I have a "test-route" from my app to get datas of a given date), and datas have been available now, but not when I received notification payload. 

 I could delay my request to 12 or 24 hours, but I would like to know which happens 

Thanks

[DorisFitbit]

Hi @Fred.A 

Thanks for submitting your request. We will check and get back to you as soon as we can. 

[Fred.A]

Thanks a lot ! 

[jjleitner]

Hello @DorisFitbit,

Are there any updates on this? I am also experiencing the same issue.

[DorisFitbit]

Hi @jjleitner 

Our internal teams are aware of the issue. I am checking in with them regularly and will let you know the moment I have news to share. Thank you!

 

[Campconroy]

What is the recommended delay before processing webhooks and is this just for body notifications or should a delay be applied before processing all notifications?