While I can confirm the problem Tuesday has observed, and I appreciate the workaround Megha has offered, that is not the correct long-term solution for this.
First though, to be clear, it's not that the pathfilter.json is ""totaly empty" but rather reset to its properties having empty values. But either way, the consequence is that after the update any existing scheduled tasks (or system probes) which "publish"/save output to a file are REMOVED on the startup which happens after the update. (And those are NOT so easily recovered, as the single neo-cron.bak is soon overwritten.)
And while the technote for this update and the previous one do warn folks (in a "known issue" bullet) to backup the neo-cron.xml before doing the update, many will miss that step and lose their tasks--with the frustration Tuesday here has shared, specifically when they DID modify the pathfilter.json, intending to PREVENT this loss of tasks.
The correct solution is that the update simply should NOT overwrite the pathfilter.json if it exists. Megha, it's not clear if you're saying you all acknowledge this and plan to change it. Sadly, even if it's fixed in some later update, this problem will bite people for weeks or even months to come, until then.
(One more thing: if a future need to replace the file is because of a need to change the layout of the file--such as to add a new path setting, there should instead be a mechanism buiit into the update to fold the current values of any existing file into that new format.)
Megha, let us know if a bug report or feature request needs to be filed to get the update to NOT overwrite the file, if present.
AdChoices