Version info:
Artillery: 2.0.30
Node.js: v24.7.0
OS: darwin
Running this command (in Azure Cloud)
artillery run-aci artillery.script.ts
I expect the tests to complete within 20/25 minutes but sometimes they get stuck until the actual Azure ADO pipeline times out.
In the logs, I see this error message being repeated over and over
"server": "Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0", "x-ms-request-id": "57605c86-c01e-0034-3768-ccd44a000000", "x-ms-client-request-id": "634e3a42-bdf8-4252-a00a-5c4fd70f8cf6", "x-ms-version": "2026-02-06", "date": "Tue, 14 Apr 2026 23:46:35 GMT", "message": "The specified blob does not exist.\nRequestId:57605c86-c01e-0034-3768-ccd44a000000\nTime:2026-04-14T23:46:35.9457662Z", "code": "BlobNotFound" }, "name": "RestError", "request": { "url": "[https://REDACTED/artillery/tests/txgbn_p4dp7qxgy95h4rnbmkk6bg5w3gwyz_3ncc/overflow/worker4jm7_jgm59gq54mqgyx57hkayrazxptnqb_3rjq/f3101b72-bcd4-4265-870a-c8f993a727e2.json",](https://REDACTED/artillery/tests/txgbn_p4dp7qxgy95h4rnbmkk6bg5w3gwyz_3ncc/overflow/worker4jm7_jgm59gq54mqgyx57hkayrazxptnqb_3rjq/f3101b72-bcd4-4265-870a-c8f993a727e2.json%22,) "method": "GET", "headers": { "x-ms-version": "REDACTED", "accept": "application/xml", "user-agent": "azsdk-js-azure-storage-blob/12.30.0 core-rest-pipeline/1.22.2 Node/24.14.1 (Linux 5.15.0-1102-azure; x64)", "x-ms-client-request-id": "634e3a42-bdf8-4252-a00a-5c4fd70f8cf6", "authorization": "REDACTED" }, "timeout": 0, "withCredentials": false, "streamResponseStatusCodes": {}, "enableBrowserStreams": false, "disableKeepAlive": false, "requestId": "634e3a42-bdf8-4252-a00a-5c4fd70f8cf6", "allowInsecureConnection": true, "tracingOptions": { "tracingContext": { "_contextMap": {} } } } } Error: Failed to fetch worker message: tests/txgbn_p4dp7qxgy95h4rnbmkk6bg5w3gwyz_3ncc/overflow/worker4jm7_jgm59gq54mqgyx57hkayrazxptnqb_3rjq/f3101b72-bcd4-4265-870a-c8f993a727e2.json at AzureQueueConsumer.handleMessage (/azp/_work/1/s/node_modules/.pnpm/artillery@2.0.30_@types+node@24.1.0/node_modules/artillery/lib/platform/az/aci.js:290:21) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async Timeout._onTimeout (/azp/_work/1/s/node_modules/.pnpm/artillery@2.0.30_@types+node@24.1.0/node_modules/artillery/lib/platform/az/aqs-queue-consumer.js:58:13)
this comment I got from my colleague from dev ops team
Artillery's ACI mode spills large queue messages to blob storage (overflow/). At phase end the straggler worker either failed to upload its final summary blob or it got cleaned up before the orchestrator fetched it. The orchestrator then retries forever instead of giving up — almost certainly an Artillery bug in aci.js:290 / aqs-queue-consumer.js:58 where a missing blob is treated as retryable with no budget.
Thanks in advance
Version info:
Running this command (in Azure Cloud)
I expect the tests to complete within 20/25 minutes but sometimes they get stuck until the actual Azure ADO pipeline times out.
In the logs, I see this error message being repeated over and over
"server": "Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0", "x-ms-request-id": "57605c86-c01e-0034-3768-ccd44a000000", "x-ms-client-request-id": "634e3a42-bdf8-4252-a00a-5c4fd70f8cf6", "x-ms-version": "2026-02-06", "date": "Tue, 14 Apr 2026 23:46:35 GMT", "message": "The specified blob does not exist.\nRequestId:57605c86-c01e-0034-3768-ccd44a000000\nTime:2026-04-14T23:46:35.9457662Z", "code": "BlobNotFound" }, "name": "RestError", "request": { "url": "[https://REDACTED/artillery/tests/txgbn_p4dp7qxgy95h4rnbmkk6bg5w3gwyz_3ncc/overflow/worker4jm7_jgm59gq54mqgyx57hkayrazxptnqb_3rjq/f3101b72-bcd4-4265-870a-c8f993a727e2.json",](https://REDACTED/artillery/tests/txgbn_p4dp7qxgy95h4rnbmkk6bg5w3gwyz_3ncc/overflow/worker4jm7_jgm59gq54mqgyx57hkayrazxptnqb_3rjq/f3101b72-bcd4-4265-870a-c8f993a727e2.json%22,) "method": "GET", "headers": { "x-ms-version": "REDACTED", "accept": "application/xml", "user-agent": "azsdk-js-azure-storage-blob/12.30.0 core-rest-pipeline/1.22.2 Node/24.14.1 (Linux 5.15.0-1102-azure; x64)", "x-ms-client-request-id": "634e3a42-bdf8-4252-a00a-5c4fd70f8cf6", "authorization": "REDACTED" }, "timeout": 0, "withCredentials": false, "streamResponseStatusCodes": {}, "enableBrowserStreams": false, "disableKeepAlive": false, "requestId": "634e3a42-bdf8-4252-a00a-5c4fd70f8cf6", "allowInsecureConnection": true, "tracingOptions": { "tracingContext": { "_contextMap": {} } } } } Error: Failed to fetch worker message: tests/txgbn_p4dp7qxgy95h4rnbmkk6bg5w3gwyz_3ncc/overflow/worker4jm7_jgm59gq54mqgyx57hkayrazxptnqb_3rjq/f3101b72-bcd4-4265-870a-c8f993a727e2.json at AzureQueueConsumer.handleMessage (/azp/_work/1/s/node_modules/.pnpm/artillery@2.0.30_@types+node@24.1.0/node_modules/artillery/lib/platform/az/aci.js:290:21) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async Timeout._onTimeout (/azp/_work/1/s/node_modules/.pnpm/artillery@2.0.30_@types+node@24.1.0/node_modules/artillery/lib/platform/az/aqs-queue-consumer.js:58:13)this comment I got from my colleague from dev ops team
Artillery's ACI mode spills large queue messages to blob storage (overflow/). At phase end the straggler worker either failed to upload its final summary blob or it got cleaned up before the orchestrator fetched it. The orchestrator then retries forever instead of giving up — almost certainly an Artillery bug in aci.js:290 / aqs-queue-consumer.js:58 where a missing blob is treated as retryable with no budget.
Thanks in advance