Comment 3 for bug 1486281

After investigation found out that timeout issues occur in following scenario:

Assume a CREATE/UPDATE of stack is in progress.
Now if a resource is stuck in [CREATE|UPDATE]_IN_PROGRESS status, and another update/delete is triggered, this new traversal will wait for the IN_PROGRESS resource to fail/complete, which will lead to timeout.

Seems like we need to bring back thread group manager, to stop the job, at least while delete. Why do we have to wait for the previous resource traversal to complete in case of delete.