@thor_landstrom & @k10shetty1 I can confirm the issue is not reproducible in the test workflow anymore.
However, it is still triggered in the original one.
That begs the question, since @thor_landstrom cannot reproduce the issue of the table reader either:
Is there something faulty happening in the originating workflow?
1 Like
