We have projects that are triggered by SCM changes. We've noticed that if there is a network failure or server maintenance (connection to SVN server can't be made), situation is handled as SVN change and project is triggered and of course failed.

When SVN server is back on-line, projects are not triggered automatically, since technically, there is no changes. This results all SCM-triggered projects show as failed until they are triggered manually -or new commits are made.