Skip to content

Change maximum delivery latency for driveItem and list#9979

Closed
chackman wants to merge 1 commit into
microsoftgraph:mainfrom
chackman:patch-1
Closed

Change maximum delivery latency for driveItem and list#9979
chackman wants to merge 1 commit into
microsoftgraph:mainfrom
chackman:patch-1

Conversation

@chackman

Copy link
Copy Markdown
Contributor

Updated delivery latency for driveItem and list to reflect unknown values.

Important

Use the AI-powered workflow for Graph onboarding to author and self-review schema-related changes. See https://aka.ms/msgraphcdk for more information.

Required for API changes:

  • [] Link to API.md file: ADD LINK HERE
  • [] Link to PR for public-facing schema changes (schema-Prod-beta/v1.0.csdl): ADD LINK HERE

Add other supporting information, such as a description of the PR changes:

There is no set maximum delivery latency; the average latency is unchanged.


Important

The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.

After you've created your PR, expand this section for tips and additional instructions.
  • do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
  • Add the ready for content review label to start a review. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
  • If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
  • After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
  • Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

Updated delivery latency for driveItem and list to reflect unknown values.
@chackman chackman added the ready for content review PR is ready for a content review - content development and tech review are complete. label Jul 14, 2026
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 4986ce0:

✅ Validation status: passed

File Status Preview URL Details
concepts/includes/change-notifications-delivery-latency.md ✅Succeeded

For more details, please refer to the build report.

@chackman chackman removed the ready for content review PR is ready for a content review - content development and tech review are complete. label Jul 14, 2026
@chackman chackman closed this Jul 14, 2026
@chackman

Copy link
Copy Markdown
Contributor Author

I will update this and create a new PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant