I would like to use the Outlook REST API webhooks / subscriptions to update calendar events in my application. I couldn't find any information in the documentation regarding whether the Outlook API will retry sending Notifications if my application is down / crashed or sends a 500 error. I know the Google API uses exponential backoff to retry sending. Does Outlook do something similar?
Thanks,
Adam
Yes. From the Microsoft Graph documentation:
When the subscribed resource changes, the webhooks facility sends a notification to your notification URL with the following payload. The notification endpoint must send a response of 200 or 204 with no response body within 30 seconds otherwise the notification attempt will be retried at exponentially increasing intervals. Services that consistently take 30 seconds or more may be throttled and receive a sparser notification set.
Related
I am implementing IAP into my app and have started using the server notifications. I am wondering is apple offer sometype of dashboard where I can see the history of past attempted notifications just like google and stripes webhook dashboards?
Thanks
There isn't any dashboard to see notifications, but If a notification failed because your server didn't handle it or returned a status code other than 200, then Apple retires 3 times.
If the App Store server doesn’t receive a 200 response from your server after the initial notification attempt, it retries [...] at 6, 24, and 48 hours after its initial attempt.
Source: https://developer.apple.com/documentation/appstoreservernotifications/your_server
Can someone tell me what the behaviour is when a Graph change notification is attempted to be sent to the configured endpoint (notificationUrl) but the endpoint is unavailable (e.g. your in the process of a release or the endpoint is just not there for a while)?
I can see that I am getting a repeated notification delivery attempt every 5 minutes, but does that eventually stop? Does it become a 'missed' lifecycle event at some stage? Or does it keep trying endlessly?
thanks
The service will retry for a few hours.
If the notification URL is unresponsive or slow for more than 10% of delivery attempts, notifications will be paused and retried in a couple of hours.
If the notification URL is unresponsive or slow for more than 20% of delivery attempts, notifications will be dropped.
Unresponsive notification URL will not result in a missed lifecycle notifications. Those are only sent when the service was not able to emit notifications due to other reasons.
After registering to webhook subscription for mail or user resources - What is the expected time between a change occur till our subscribed endpoint will receive the change notification?
The time to deliver notifications varies depending on the service load and other factors. Under normal conditions you should receive notifications within 5 minutes of the actual change.
I'm working on a sync server that keeps the Office 365 events and my calendering app in sync. I subscribed to a push notification for user's event calendar that has a custom single extended property.
The documentation says if the sync server doesn't respond with a 2xx message, the notifications will be resent in periodic intervals. I tried by bringing my server down for some time and in this interval I did some changes to the events for which I was expecting notifications. Then I brought the server up again and it took some time(10-15 mins) for Microsoft to send old queued notifications.
Any idea what is the interval that Microsoft sends queued notifications when 2xx is not received?
I'm building a simple slack bot and can currently send private messages as well as checking for the last 10 messages received within this one-to-one channel.
Is there a way of getting a POST notification to my webservice whenever the user replies, instead of having to poll and continuously check messages on that one-to-one channel?
Now you can make use of Slack events to receive notifications.
In the give use-case, 'Message' event can be used to capture message received and process accordingly.
https://api.slack.com/events/message
Bots generally work by connecting to the real-time messaging API, a WebSocket-based API that sends you events as they happen. Specifically, you should see a message event sent to you every time a message visible to your bot is sent.
To answer your question, there's no way to get an HTTP POST sent to you instead; you'll need to connect to the RTM API and listen for events that way.