# Which workflow methods can cause thread of execution to change?

**URL:** <https://community.temporal.io/t/which-workflow-methods-can-cause-thread-of-execution-to-change/19251>\
**Category:** Community Support\
**Tags:** java-sdk\
**Created:** [February 5, 2026, 2:55pm UTC](https://community.temporal.io/t/which-workflow-methods-can-cause-thread-of-execution-to-change/19251 "2026-02-05T14:55:29Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![awwx](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/awwx/32/8185_2.png) [@awwx](https://community.temporal.io/u/awwx)\
**Post date:** [February 18, 2026, 8:49am UTC](https://community.temporal.io/t/which-workflow-methods-can-cause-thread-of-execution-to-change/19251/3 "2026-02-18T08:49:23Z")

</div>

See [How does workflow thread synchronization work? - #2 by maxim](https://community.temporal.io/t/how-does-workflow-thread-synchronization-work/504/2)

I read this to mean that non-blocking methods don’t yield.

---

_[View the full topic](https://community.temporal.io/t/which-workflow-methods-can-cause-thread-of-execution-to-change/19251)._