Does anyone know why the ‘Transfer to Queue’ node logs as abandoned immediately?
The flow logic is correct, yet the metric spikes. The configuration is standard.
node_type: transfer_to_queue
queue_id: 550e8400-e29b-41d4-a716-446655440000
skip_wait_time: false
allow_callback: true
The environment is EU Frankfurt. The agents are available, but the dashboard counts the transfer as a drop.
I normally fix this by ensuring the transfer_type is explicitly set to queue in the configuration, rather than relying on defaults that might interpret it as a direct transfer or external call depending on the platform version.
The immediate abandonment metric often triggers when the system fails to locate a valid queue context or when the skip_wait_time logic conflicts with agent availability states. In EU Frankfurt, latency can also cause premature timeout detection if the retry policy is too aggressive. Try adding retry_on_failure: true and checking if the queue ID matches the exact resource ID from the API, not just the dashboard display ID.
resource "genesyscloud_routing_queue" "my_queue" {
id = "550e8400-e29b-41d4-a716-446655440000"
# Ensure this matches the flow node config
transfer_to_queue {
queue_id = "550e8400-e29b-41d4-a716-446655440000"
skip_wait_time = false
allow_callback = true
transfer_type = "queue"
}
}
Validate the queue status via CLI to confirm it is active and accepting transfers.