This problem could occur when two users are simultaneously deleting orphaned routes and associating (currently orphaned) routes with applications. The problem is that the CLI checks for orphaned routes and then deletes them (just before which they could have been associated with applications).
I believe this cannot be fixed unless CC issue 527 is implemented.