Share via

Issues with Lookup Node in Azure PromptFlow Standard QnA Prompt

Charmaine Hlongwane 0 Reputation points
2025-01-07T08:47:30.7566667+00:00

I am encountering issues with the lookup node in one of the standard QnA prompts provided by Azure PromptFlow. I was building on top of this drag-and-drop component and noticed the following challenges:

Deprecation Warnings:

The execution logs include multiple deprecation warnings, such as the use of dict (deprecated in Pydantic V2.0) and FileType Enum. These warnings appear to be tied to internal logic within the lookup node. Since the node is part of the standard template, I do not have access to its raw code to address these issues myself.

424 Failed Dependency Error:

When making API calls to my endpoint for the deployment of this prompt flow, I consistently receive a 424 Failed Dependency error.

Could this error be caused by the lookup node or related configuration issues stemming from the deprecation warnings?

What steps should I take to resolve this error and ensure my deployment and endpoint work as expected?

Since the lookup node is a standard drag-and-drop feature, I would greatly appreciate your guidance on the following:

How to handle or bypass the deprecation issues within the lookup node.

Detailed troubleshooting steps for addressing the 424 Failed Dependency error.

Please let me know if you need additional details about my configuration, logs, or the specific steps I took to reproduce the issue.

Azure AI Search
Azure AI Search
An Azure search service with built-in artificial intelligence capabilities that enrich information to help identify and explore relevant content at scale.
1,141 questions
Azure OpenAI Service
Azure OpenAI Service
An Azure service that provides access to OpenAI’s GPT-3 models with enterprise capabilities.
3,503 questions
Azure AI services
Azure AI services
A group of Azure services, SDKs, and APIs designed to make apps more intelligent, engaging, and discoverable.
3,040 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Azar 25,375 Reputation points MVP
    2025-01-11T12:14:39.27+00:00

    Hi there Charmaine Hlongwane

    Thnx for using QandA platform

    the deprecation warnings starts from the standard template’s internal logic, they are unlikely to directly cause the 424 error but could signal outdated dependencies affecting functionality. and for the 424 error, verify that all dependent services eg., Azure AI Search or OpenAI Service are correctly configured and accessible.

    For now, consider testing an alternative workflow without the lookup node to isolate the issue. Suggest you to raise a support req for the same.

    https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview

    If this helps kindly accept the answer thanks much.

    0 comments

Your answer

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