Azure CLU works in Postman but Health Bot fails with clu_result is not defined

Suma Nalluri 40 Reputation points
2026-02-25T19:46:47.8033333+00:00

Hi,

I’m encountering an issue while integrating Azure Conversational Language Understanding (CLU) with a Health Bot scenario.

The CLU analyze-conversations runtime call works correctly when tested externally (returns 200 OK with valid intent predictions). However, within the Health Bot flow, the CLU node executes but the subsequent Switch step fails with:

Call for LU model failed. error: DialogContextError: cluResponse is not defined

This behavior suggests that the CLU result variable is not being created at runtime.

I have already verified the following:

• CLU runtime endpoint is reachable and functional • Model is trained and deployment is successful • Project and deployment configuration are correct • Input utterance binding tested with both dynamic and hardcoded values • Flow wiring and success paths are configured correctly

Since the same CLU runtime call works outside the bot but fails to produce a result variable inside the flow, I’m trying to understand what might cause this discrepancy.

Any insights or troubleshooting suggestions would be appreciated.Screenshot 2026-02-25 143529

Screenshot 2026-02-25 144054

Screenshot 2026-02-25 143518

Azure Health Data Services
Azure Health Data Services

An Azure offering that provides a suite of purpose-built technologies for protected health information in the cloud.


Answer accepted by question author
Manas R Mohanty 17,270 Reputation points Moderator
2026-03-11T16:07:17.8833333+00:00

Hi Suma Nalluri

Thank you for confirming via Support ticket that you were able to resolve the issue with hints provided from support side.

Attached case summary for reference.

Issue reported

DialogContextError: cluResponse is not defined

Recommendation shared from Support

Suggested to cross check endpoint/model name

Suggested to test language resource

Recommendation shared from PG

 “(cluResponse.result.prediction.topIntent) was not valid at resource side and suggested to cross check this node

Status: Customer was able to figure out the issue with pointers shared.

Please take a minute to accept this answer as verified if you appreciated our inputs.

Thank you.

Was this answer helpful?

0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.