Retention excecution activity log #600
Merged
Conversation
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
Bionic711
reviewed
Jan 16, 2026
Bionic711
approved these changes
Jan 16, 2026
Collaborator
Bionic711
left a comment
Bionic711
left a comment
There was a problem hiding this comment.
Just the one question about the lack of general exception handling in the one call.
Now uses retention_policy_next_run timestamp - Compares current time against the stored next scheduled time. If current time >= next scheduled time, it runs. Reduced check interval from 1 hour to 5 minutes - More responsive scheduling, ensures it catches the scheduled time promptly. Better fallback logic - If next_run can't be parsed, falls back to checking last_run (23-hour threshold). Runs immediately if never run before - If there's no last_run or next_run, it will execute on the first check.
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.
(v0.235.022)
Bug Fixes
last_updatedfield, but query was looking forlast_activity_at(used by conversations).YYYY-MM-DDTHH:MM:SSZbut query used Python's.isoformat()with+00:00suffix.partition_field='user_id'caused query errors.deletion_reasonparameter instead ofadditional_context.functions_retention_policy.py(query field names, date format, SELECT clause, activity logging).delete_aged_documents(), retention policy execution, Cosmos DB queries)