Hello, community!
In the Forge app I’m developing, I need to read many work items and set properties in bulk to optimize JQL searches. To achieve this, I’m using the Async Events module and handling property reads/updates in the background via the bulk set properties endpoint.
However, I’ve noticed an issue: even though this is an asynchronous task, if I try to run it again (on different work items), I receive a 400 response saying the request failed because another operation is already running in the background.
This forces me to poll the running tasks every few seconds until one finishes, and then repeat the process until all work item properties are updated. This introduces a significant runtime bottleneck.
It seems like there should be a way to queue multiple tasks, which would not only simplify my code but also reduce load on the system, instead of constantly checking and retrying tasks.
Has anyone found a way to handle multiple bulk property updates efficiently without blocking or polling?