Good to know! When you repro the problem again with a debugger attached and see UWidgetComponent::UpdateBodySetup being called from the worker thread, can you inspect and share the callstack from the GameThread? I’d like to see which ParallelFor is kicking off the work resulting in that callstack.
I’m also curious why the BodySetup was not created sooner. I see that under normal circumenstances the BodySetup is created on RegisterComponent executed on the GameThread, so then it wouldn’t have the Async object flag. Depending on the GameThread callstack we’ll get closer to understanding whether this is an engine bug or not.