I need to troubleshoot why the unit test I added passes locally, but fails here

Could it be the Python version we have running locally, versus the one used in the CI pipeline?

============================= test session starts ==============================
platform linux -- Python 3.9.21, pytest-7.4.4, pluggy-1.5.0 -- /home/runner/.cache/pypoetry/virtualenvs/iwf-python-sdk-szf-DUJx-py3.9/bin/python
cachedir: .pytest_cache
rootdir: /home/runner/work/iwf-python-sdk/iwf-python-sdk
plugins: env-0.8.2, anyio-3.7.1, cov-4.1.0
collecting ... collected 22 items

Locally I have:

❯ python3 -V
Python 3.13.2

Could it be the Python version we have running locally, versus the one used in the CI pipeline?

============================= test session starts ==============================
platform linux -- Python 3.9.21, pytest-7.4.4, pluggy-1.5.0 -- /home/runner/.cache/pypoetry/virtualenvs/iwf-python-sdk-szf-DUJx-py3.9/bin/python
cachedir: .pytest_cache
rootdir: /home/runner/work/iwf-python-sdk/iwf-python-sdk
plugins: env-0.8.2, anyio-3.7.1, cov-4.1.0
collecting ... collected 22 items

Locally I have:

❯ python3 -V
Python 3.13.2

It seems to be flaky since I can't fully control if the search attributes have been set before I query for them. I added a comment on how this could be improved with with wait_for_state_execution_completed, but this is yet to be implemented