TestPlan script often try to delete the Post or Topic that has already been deleted.

Script performs deletion of random topics. Due to multithreading it’s well possible for several threads (virtual “users”) to try to delete the same Post or Topic. As a result second thread fails with 403 error. This situation may well happen in real world but these errors complicate analysis of load test results.
Probably, we should improve the script to avoid this situation.
Similar situation may well happen with MoveTopic and even with OpenRandomTopic and so on.

Possible approaches:

1. Use JMeter Critical Section Controller to eliminate threads interference. May lead to uneven load distribution and slow down the script. Also doesn't work for several instances of JMeter (distributed launch)
2. Thread (virtual user) should delete and move only Posts/Topics that it has created earlier. It is not a real world behavior, but it may well be acceptable from the load testing perspective. There is no garanty that post/topic, created by particular thread wil be found in target branch/topic.