Process Drive folder uploads asynchronously in a worker#38
Merged
Conversation
wailbentafat
approved these changes
Apr 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR moves Google Drive folder imports out of the request/response cycle and processes them asynchronously in a dedicated worker.
What changed
upload_group_workerprocessing_statusprocessed_photo_countfailed_photo_counterror_messagerun-workersstorage_cleanersettings for Pydantic v2Why
Previously, folder-based Drive imports were processed synchronously inside the HTTP request, which made large folder uploads slow and blocking.
Now the API returns quickly, and the import is handled in the background by a worker.