Perhaps you can explicitly deploy the saved search first in your deploy. Still annoying, but a workaround.