We think we finally nailed this one down. The double “Suspended Job” entries in the history log led us down a path where we discovered that both calls would be operating on the same instance of the task collection object and could cause the task state counts to get messed up. After we fixed this, we couldn’t reproduce the problem anymore. This fix will be included in beta 13, so hopefully that solves this problem once and for all.