Hi @barn4k, this was always an undocumented API and it’s expected to change without notice.
That said, n8n still sends requests to the /rest/executions-current endpoint for me, even in v1. So you should still be able to hack your way around this.
A cleaner solution would be the use of a queue though as suggested by @BramKn over here? So perhaps you want to send the relevant data every 5 minutes to a queue in your main workflow, then have a separate workflow consuming the queue?