Asynchronous building block bulk operations
J
Johannes Schwandke
Currently requests to the bulk endpoints for building blocks (e.g. bulk-upgrade) run into timeout issues, because all selected building blocks are processed sequentially before generating the response. This easily leads to timeouts for those requests when bulk-processing multiple hundreds or even thousands of building blocks.
It would be helpful to have an endpoint, which does not wait for calculating the response with a state of each of the building blocks, but rather only accepts the request and responds back immediately. The bulk operation (i.e. upgrade) on the building blocks can then be further be processed asynchronously in the backend.
Thomas Abbe
Related to
https://support.meshcloud.io/support/tickets/2555
Janny the AI Product Manager
Thanks for taking the time to write this up — the timeout behavior and the sequential processing detail are super clear and helpful.
An async “accept + process in the background” bulk endpoint makes a lot of sense for hundreds/thousands of building blocks. I’ll share this with the team.
To help us understand the best shape for this, could you share:
1) Roughly how many building blocks you typically process per request (and your current timeout limit)?
2) How you’d prefer to track progress/results (e.g., return a job ID and poll a status endpoint, webhook/callback, or something else)?
3) Do you need per-building-block result details (success/failure + reason), and if so, how long should those results be retained?
If you have an example request/response or logs showing the timeout, feel free to paste those too.