Thanks very much for pointing this out

I included that as is for a sanity check, sure enough nothing weird happens.

But it turns out that I have a bunch of interop with JS and I think the I am setting up a event watcher inside a JS object on the start of every test (AWS Logger has its own event system to listen for Auth events inside the library, this gets setup on each test and starts a flow each time)

why this is duplicating the test/s is still TBD but I am on a trail, hopefully to a fix

You could put something like (js/console.trace "here") to places where you create an async-flow.

Yeah I added a bunch of logging and the Logger was setting up more than once. I moved it to a defonce an put that code in a new NS. All seems well now

I am noticing odd behavior around wait-for when using a vector of more than one

so i just removed that and removed the other wait-for calls (I had three in the test)

this seems to have fixed the tests

but it still leaves me with a lot of questions