Fetch restore request based on last fetched request - #45635
Open
chkp-arvidb wants to merge 3 commits into
Conversation
content-bot
changed the base branch from
master
to
contrib/chkp-public-forks_av-106336-fix-restore-request-timing
August 24, 2026 14:44
Contributor
|
Thank you for your contribution. Your generosity and caring are unrivaled! Make sure to register your contribution by filling the Contribution Registration form, so our content wizard @kamalq97 will know the proposed changes are ready to be reviewed. |
Contributor
|
Hi @chkp-arvidb, thanks for contributing to the XSOAR marketplace. To receive credit for your generous contribution please follow this link. |
Contributor
🤖 AI-Powered Code Review AvailableHi @kamalq97, you can leverage AI-powered code review to assist with this PR! Available Commands:
|
…-timing' into av-106336-fix-restore-request-timing
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.
Contributing to Cortex XSOAR Content
Make sure to register your contribution by filling the contribution registration form
The Pull Request will be reviewed only after the contribution registration form is filled.
Status
Related Issues
relates: https://jira-dc.paloaltonetworks.com/browse/CIAC-17782
Description
Fixes an issue in the Check Point Harmony Email and Collaboration (HEC) integration where restore request incidents could be missed during fetch.
Previously,
fetch_restore_requestsadvanced a single shared cursor to the newest fetched record (or to "now" on empty fetches), so restore requests that were not yet available in the searchindex — or that belonged to a less busy SaaS app — could be skipped permanently.
Changes:
last_rr_fetch) is now tracked per SaaS app, so a busy app no longer drags the cursor forward past unfetched records of another app. Existing single-cursorstate is migrated on upgrade.
restoreRequestTimeof the newest incident actually emitted for that app; apps with no results keep their previous cursor (bounded by a 1-day maxlook-back).
max_fetch, keeping the oldest records on truncation.fetch_incidentsandfetch_restore_requestsfor troubleshooting fetch windows, cursors, and truncation.Must have