Before
An administrator would need to stop the existing monitoring channel, calculate a suitable expiration time, and create a new watch on a recurring schedule. This manual renewal process could create delays or monitoring gaps if the channel was not refreshed in time.
How it works
- A scheduled run begins the renewal process for Google Drive upload activity.
- The current watch is stopped and a new expiration time is calculated for the replacement monitoring window.
- A new activity watch is created and configured to send upload notifications through a webhook channel.
Workflow details
- Scheduled monitoring: The workflow runs on a predetermined schedule to maintain ongoing visibility into Google Drive upload activity.
- Existing channel cleanup: It stops the current monitoring channel before creating a replacement, preventing conflicts when only one watch channel can exist for the monitored resource.
- Expiration calculation: It calculates a new expiration time by adding six hours to the current time, providing a defined validity window for the renewed watch.
- Watch renewal: It starts a new activity watch for Google Drive upload or add-to-folder events and connects notifications through a webhook channel.
- Operational result: The monitoring configuration is refreshed automatically so upload activity can continue to be observed without requiring repeated manual setup.
What changed
Watch renewal is now handled automatically on a schedule: the existing channel is stopped, the six-hour expiration window is calculated, and a replacement upload monitor is created without requiring an administrator to perform each setup action manually.
Work removed
Stopping the existing watch, calculating the next expiration time, recreating the Google Drive upload watch, and configuring the notification channel at each scheduled renewal.
Expected outcome
The workflow can remove up to three recurring manual setup actions per renewal and help maintain continuous upload monitoring across each six-hour watch window.
