Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Drive Sheets webhooks might not always be triggered or processed. #2569

Open
mbertrand opened this issue Feb 9, 2023 · 2 comments
Open
Assignees
Labels
Bug Something isn't working

Comments

@mbertrand
Copy link
Member

mbertrand commented Feb 9, 2023

Steps to Reproduce

Not all sheets seem to get processed by the xpro webhook endpoint when changes are made. We should try to determine if the webhook endpoint was hit but errored, or never called at all, for these sheet ids.

@mbertrand mbertrand added the Bug Something isn't working label Feb 9, 2023
@mbertrand mbertrand self-assigned this Feb 9, 2023
@mbertrand
Copy link
Member Author

The webhook endpoint was hit for all google sheet ids in the above tickets at least once, with a 200 response code.

Some (but not all) of these sheets have error events under:
Current file watch in the database for Coupon Assignment sheet is expired. Some file changes may have failed to trigger a push notification
or
sheets.tasks.schedule_coupon_assignment_sheet_handling - 'dict' object has no attribute 'replace' - should be fixed by #2565

@mbertrand
Copy link
Member Author

On RC, when new GoogleFileWatch objects are created, the expiration date is the same as the activation date. I had to manually run manage.py setup_file_watch --sheet-id <sheed_id> --sheet-type enrollassign --confirm to get it to process. Will look further into this later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant