Replacement for the executions-current endpoint?

I have been using the executions-current endpoint to prevent concurrent executions of workflows in previous versions of n8n.
As per @jan 's solution.
See Multiple webook calls overlaping

Given the release of the public n8n API I just wanted to check this was still “best practise” for the latest n8n release.
I can’t find a replacement endpoint in the public API but just wanted to check.

Any help much appreciated :slight_smile:

Hey @beaspider,

Just checked and it looks like the API doesn’t provide currently running executions so what you are doing is still one of the ways you can check.