When i clone pipeline job with enabled Perforce polling, i receive new job with new name, but hidden polling settings cloned too. And this polling settings do not update state even in manual first run. So i receive unusable job triggered by submits/changes in another SCM branch. Weak workaround - disable polling before cloning or manual create new job. I do not test this issue with another SCM.