Avoiding Progress "bleed" from /sdapi/v1/progress API endpoint

[chrisbward]

Hi,

I've recently built a frontend for A1111 using the API, and built a feature to emulate the progress you see in A1111 - but what I've found is that if two requests are sent, polling for the progress may show a job being rendered to the wrong issuer.

Of course this could probably be mitigated with a token, but couldn't find anything in the code that would allow for this - wondering if anyone knows of a way to solve this?

API documentation is a little behind/broken, but mostly ok.

Chris