Status Update
Comments
bl...@google.com <bl...@google.com> #2
Metadata
- Summary: The Directory API's users.list method is inconsistently returning a nextPageToken when using the query parameter, and the starts with operator is not working for the orgDepartment field.
- Tags:
,directory-api ,users-list ,next-page-token ,query-parameter ,org-department starts-with-operator
Additional resources:
https://issuetracker.google.com/savedsearches/566232?hl=it https://developers.google.com/drive/api/reference/rest/v3/files/list https://developers.google.com/admin-sdk/directory/v1/.../manage-users https://developers.google.com/admin-sdk/directory/reference/rest/v1/.../list https://stackoverflow.com/.../want-admindirectory-users-list-more-then-500... https://stackoverflow.com/.../drive-list-files-doesnt-have-nextpagetoken-wh... https://stackoverflow.com/.../how-to-resolve-the-missing-information-probl...
pb...@bigid.com <pb...@bigid.com> #3
Automated by Blunderbuss job workspace-devrel-public-issue-tracker-blunderbuss-autoassigner for config assign for component 191635.
Description
I am using this API method ->
Worked for several months, until yesterday around 3pm EST, the webhook seemed to terminate and no incoming traffic was received. We even checked the gateway that sits in front of our webhook. This is quite unusual since we typically see around half a million to a million events per day.
The drive webhook is created from an apps script that uses the Admin SDK, AdminReports.Activities.watch() method which internally calls the API method mentioned at the top. We don't specify any expiration in our request, therefore, our watch channel should default to the 6 hours mentioned in the documentation. However, a few minutes after the watch is created, no traffic is received in the channel. This is quite unsual from the activity we've seen historically.
Is this a bug that can be looked at and resolved quickly?
Here are a few links to the documentation: