I have a setup where multiple jobs poll a single URL's modification time, in "H * * * *". The expected behavior would be for all jobs to trigger throughout the hour after the change is detected. What actually happens is the first job to poll and detect the update will trigger the job, but later jobs' polls will detect "no changes".

This suggests the backend is keeping a global URL->attributes array which is updated as each of the polls run. I believe instead the attributes used to detect changes should be per-job, or at least an option to switch between global or per-job.

A workaround would be to add ?[unique string] to each of the jobs' URLs, but this will not be possible in all cases.