Increase webhook subscription from 3 days to about 6 months
From the developer's view, ideally the webhook subscription will never expire. But that's probably not practical.
The next best would be say 6month expiry. Because that means we still need to build a re-scheduling mechanism. But we don't have to run it every 3 days.
I believe if the expiry was too long say 1 or 2 years, the developers will leave without building a re-scheduler, so the webhook will just break in 1 year's time.
Currently, because the webhook subscription expires every three days, we are driving a behaviour where developers don't use webhooks - they just use scheduled polling on the delta queries. Which is less efficient, event is delayed, and possibly more waste.
Scheduled polling is extremely easy to do on Functions and Flow, which diminishes the benefits of webhooks.
We are working on extending the webhooks framework with new functionality, and this will also allow us to increase subscription lifetime. -EY