# After modifying the selections, distill should update its database immediately **URL:** \ **Category:** Help and Support\ **Tags:** feature-request\ **Created:** [November 10, 2026, 5:50pm UTC](https://forums.distill.io/t/after-modifying-the-selections-distill-should-update-its-database-immediately/6180 "2026-11-10T17:50:38Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![jaddorf](https://forums.distill.io/letter_avatar_proxy/v4/letter/j/9dc877/32.png) [@jaddorf](https://forums.distill.io/u/jaddorf)\ **Post date:** [November 10, 2026, 5:50pm UTC](https://forums.distill.io/t/after-modifying-the-selections-distill-should-update-its-database-immediately/6180/1 "2026-11-10T17:50:38Z")
After I edit the selections for an existing monitor, Distill reports its next crawl of the page as a change – but I don’t think it should since I manually changed the target selection. I would think Distill would immediately save the NEW selection info when you edit the monitor and then use that new info to perform its compare at the next crawl. Right now Distill does not report its first crawl after a monitor CREATION as a change - which makes sense. I think it shouldn’\t report its first crawl after a monitor EDIT either. Thanks!! ---
**Author:** ![srijith](https://forums.distill.io/letter_avatar_proxy/v4/letter/s/c77e96/32.png) [@srijith](https://forums.distill.io/u/srijith)\ **Post date:** [November 11, 2026, 7:23am UTC](https://forums.distill.io/t/after-modifying-the-selections-distill-should-update-its-database-immediately/6180/2 "2026-11-11T07:23:37Z")
@jaddorf This is expected behavior. Distill compares the content captured during each check with the content saved from the previous check.When you edit a monitor’s selection, Distill updates the selection rules but does not overwrite the previously captured content. On the next check, it extracts content using the new selection and compares it with the last saved version. Since the selected content may now be different, Distill records it as a change and establishes the new baseline.For a newly created monitor, there is no previous version to compare, so the first check becomes the baseline and is not reported as a change. Thank you for the feedback. We understand why treating the first check after a selection edit as a new baseline could be useful, and we’ll share this suggestion with the team. ---
**Author:** ![jaddorf](https://forums.distill.io/letter_avatar_proxy/v4/letter/j/9dc877/32.png) [@jaddorf](https://forums.distill.io/u/jaddorf)\ **Post date:** [November 11, 2026, 4:37pm UTC](https://forums.distill.io/t/after-modifying-the-selections-distill-should-update-its-database-immediately/6180/3 "2026-11-11T16:37:06Z")
I appreciate your response - my suggestion does seem logical (to me.. 🙂 ) Best wishes! /jim ---
**Author:** ![ajitk](https://forums.distill.io/letter_avatar_proxy/v4/letter/a/ec9cab/32.png) [@ajitk](https://forums.distill.io/u/ajitk)\ **Post date:** [November 12, 2026, 2:29am UTC](https://forums.distill.io/t/after-modifying-the-selections-distill-should-update-its-database-immediately/6180/4 "2026-11-12T02:29:03Z")
it makes sense when users update their selections to fine-tune what gets monitored. but sometimes they are just fixing an error or a mistake and still want to catch any changes since the last successful check. one option is to invalidate the existing change history whenever selections change and start tracking from a fresh baseline. does that sound reasonable, or would it be too drastic in some cases? ---
**Author:** ![jaddorf](https://forums.distill.io/letter_avatar_proxy/v4/letter/j/9dc877/32.png) [@jaddorf](https://forums.distill.io/u/jaddorf)\ **Post date:** [November 12, 2026, 3:27am UTC](https://forums.distill.io/t/after-modifying-the-selections-distill-should-update-its-database-immediately/6180/5 "2026-11-12T03:27:59Z")
I wrote in because clearly the behavior after editing selections should match that of initial setup – to me it makes no sense to notify of a change after you have visually reviewed the web page and modified the selections. Think of the work flow: you are editing an entry because you were notified of changes – but it is a false report so you edit the entry to fix up the selection. Then in xx minutes you get a notification of a change so you go back into Distill to see what the change was and find out it wasn’t a real change from the last time you reviewed the page (when you edited your selections) but instead just the database storing your new selections. Illogical to this retired programmer. The new selections should be stored when you save the selections as they are on initial setup of the monitor. But also not a big deal 🙂 I’m not sure I understand your question - is the function of “resetting” the stored data available or are you suggesting maybe adding it? I can’t think of a work flow that would want a change notification immediately/shortly AFTER an edit. Thank you for your tool!