Workflow pollution is this meant to happen?
I encountered today for the first time that when I run multiple of the same workflow at the same time, there was context from one leaking into another, for example something like,
Crawl data appears contaminated with details for an unrelated business (xxxxxxxx), which do not belong to xxxxx and
should not be used for this verification. Is this a feature or a bug or is my base assumption that I should be able to call a workflow and it have its context and state isolated, an incorrect assumption?
