Microsoft-graph-docs: Incorrect max value limit set for User, calendar, contacts, etc. subscriptions - not a DOCS issue!

[tfrancois]

Please please please....can someone at Microsoft correct this please. Everywhere in the documentation it states that the max subscription time is 3 days for user, calendar, contacts subscriptions, etc. This is 4320 minutes = 72 hours = 3 days. BUT!!!!! The error message that gets returned when you try to set this max value is:

"error":{ "code":"ExtensionError", "message":"Subscription expiration can only be 4230 minutes in the future.", "innerError":{ "request-id":"48f13973-XXXX-XXXX-XXXX-161XXXX783df", "date":"2018-08-20T02:29:38" } }

For whatever reason, the max threshold value is INCORRECTLY set to 4230 rather than 4320. It has been corrected for Drive #2851 but not for the others?????

Resource | Maximum Expiration Time
-- | --
Mail | 4230 minutes (3 days)
Calendar | 4230 minutes (3 days)
Contacts | 4230 minutes (3 days)
Group conversations | 4230 minutes (3 days)
Drive root items | 4320 minutes (3 days) => CORRECT VALUE

Is this carelessness on Microsoft's part? Why the difference in minutes even though the threshold is stated as 3 days for all object types. This creates issues for developers when trying to set a correct max subscription time via mathematical computation (again: 3 days = 72 hours = 4320 minutes) HENCE when you try new Date() + 4320 minutes the request returns the error above. Can we just fix this ONCE and for all. It's either 3 days OR 4230 minutes. The 2 are not functional or mathematical equivalents.

Furthermore, it is not acceptable to fix documents in SOME places to reflect the INCORRECT value, it is much more feasible to fix the incorrect value in the back end so that it aligns with the consensus 3-day limit. Why would it be corrected for OneDrive/Drive and not for the others?

See Maximum length of subscription per resource type section of link official doc link below:
https://developer.microsoft.com/en-us/graph/docs/api-reference/beta/resources/subscription

PLEASE FIX THIS. Three (3) days is 4320 minutes. It should be consistent for all subscriptions.

Thank you.

[angelgolfer-ms]

Hi @tfrancois , the documentation issue in the subscription resource topic has been fixed, for v1.0 and beta. Thanks for bringing this up.
As for the reference of "4230 minutes" in the service-generated error message, the best venue to get traction for service-side issues is raising a support ticket. Please do so on the Azure Portal where you registered your application. This simple video shows how to file it properly by visiting here.

Would you report the issue there please?

I am going to close this issue here, as the doc-side bug is fixed, and the Microsoft Graph Github issues list is for documentation issues. Thank you for your support!

[tfrancois]

@angelgolfer-ms Thank you for replying Angel but correcting the documentation is so counter-productive, if you don't mind respectfully saying. The issue is the API currently reports an error probably because of a typo/transposition of the max value in the underlying code and that is what should be resolved if 3 days is in fact the intended maximum subscription lifespan. In my humble opinion, this will only create more confusion and angst for developers like myself who rely on accuracy of documentation from the source. Wouldn't your input/feedbck to your counterparts at Microsoft be more successful and responsive than if I log it myself? (I will btw just asking if you can take it a step further as well. Please.)

Thank you regardless for your efforts.

[angelgolfer-ms]

Hi @tfrancois,
:-). In the spirit of transparency - I have tried to reach out internally to get the error message fixed but haven't heard back yet. Having the valued customer, you, open a support ticket is an alternative, and sometimes gets traction sooner. Thank you!