Subscriber stopped making requests

[Zoinksberg]

Hello,

I have a subscriber for app 23RD5Q.  It suddenly stopped making requests on 1/13 even though all requests made were successful up until then.  I deleted the original subscriber and verified a new one but there's still no requests being made.

Could this be looked into?  Thanks

[Gordon-C]

Hi @Zoinksberg 

We don't store log data back that far for me to investigate why it originally stopped.   In our documentation, Disabled Subscribers, we explain the reason the subscribers get disabled and how to re-enable them.   To my recollection, we didn't have an outage around that time.   Since you deleted the subscriber and recreated it, I think you need to go through the process of recreating all of the subscriptions again.  Have you tried that?

[Zoinksberg]

I did do that and re-enabled it.  My subscriber had 100% success rate and there were no reasons why it should have stopped.

I've added a new subscriber and verified it.  Even with the new subscriber, no requests are being made.

Here you can see my new subscriber was verified on Jan. 29th (3 days ago)

Verified 3 days ago

Clicking into the details shows that no requests have since been made.

No requests being made despite being verified 3 days ago

[Gordon-C]

Hi @Zoinksberg 

Have you created subscriptions for each of your users that point to the new subscriber?

[Zoinksberg]

I have but I realize I'm getting a validation error for `subscriberId`.  The documentation doesn't provide any details about this parameter.  Here is the error:

{\"errors\":[{\"errorType\":\"validation\",\"fieldName\":\"subscriberId\",\"message\":\"Invalid parameter subscriberId: null\"}]}

[Gordon-C]

Would you provide the syntax you're using to create the subscriptions, including the headers?

[Zoinksberg]

I'm making POST requests to:

- https://api.fitbit.com/1/user/-/sleep/apiSubscriptions/1-sleep.json

- https://api.fitbit.com/1/user/-/activities/apiSubscriptions/1-activities.json

The only header is the Authorization header with the Bearer token.

[Gordon-C · Accepted solution]

Ok.   Try these steps to see if it works for you.

1. Call Get Subscription List endpoint (https://dev.fitbit.com/build/reference/web-api/subscription/get-subscription-list/) for each user to see if an existing subscription.

2. If the user has a subscription, delete it using the Delete Subscription endpoint (https://dev.fitbit.com/build/reference/web-api/subscription/delete-subscription/).  You can use the Get Subscription List endpoint in step 1 to confirm the delete was successful.

3. Create a new subscription for each user using the Create Subscription endpoint (https://dev.fitbit.com/build/reference/web-api/subscription/create-subscription/).  This time, include the header X-Fitbit-Subscriber-Id and set it to your subscriber ID.  I know the documentation states you don't need to specify the header and the default subscriber will be specified, but try it anyway to see if it helps.

Let me know what happens.

[Zoinksberg]

Thank you!  Including the `X-Fitbit-Subscriber-Id` fixed the issue.