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.
@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.
)