Architect flow deployment fails with 400 on Queue Assignment

Stuck on a 400 Bad Request when pushing Architect flow updates via GC CLI v3.2.1.

The flow attempts to route to a queue using a dynamic variable that resolves correctly in the simulator but fails during the API validation step.

Error snippet:

{ "error_code": "bad_request", "message": "Queue reference invalid for region ap-southeast-2" }

Is the CLI caching outdated queue IDs or is this a known bug with dynamic variable resolution in this region?

You need to hardcode the queue ID instead of relying on a dynamic variable, as the CLI validator lacks the runtime context to resolve it.

{ “error_code”: “bad_request”, “message”: “Queue reference invalid for region ap-southeast-2” }

WFM schedules depend on static queue targets for accurate adherence tracking, so fixing this ensures your reporting stays clean.