Merge pull request #5631 from sdgilley/patch-9

Update prompt-flow-troubleshoot.md

Author: prmerger-automator[bot]

articles/ai-foundry/how-to/prompt-flow-troubleshoot.md

@@ -67,16 +67,12 @@ You might encounter a 429 error from Azure OpenAI. This error means that you rea
 
         If you see the message `request canceled` in the logs, it might be because the OpenAI API call is taking too long and exceeding the time-out limit.
 
-        A network issue or a complex request that requires more processing time might cause the OpenAI time out. For more information, see [OpenAI API time out](https://help.openai.com/en/articles/6897186-timeout).
-
+        A network issue or a complex request that requires more processing time might cause the OpenAI time out.
+     
         Wait a few seconds and retry your request. This action usually resolves any network issues.
 
         If retrying doesn't work, check whether you're using a long context model, such as `gpt-4-32k`, and set a large value for `max_tokens`. If so, the behavior is expected because your prompt might generate a long response that takes longer than the interactive mode's upper threshold. In this situation, we recommend that you try `Bulk test` because this mode doesn't have a time-out setting.
 
-1. If you can't find anything in logs to indicate that it's a specific node issue:
-
-    - Contact the prompt flow team ([promptflow-eng](mailto:[email protected])) with the logs. We try to identify the root cause.
-
 ## Compute session failures that use a custom base image: Flow deployment-related issues
 
 ### How do I resolve an upstream request time-out issue?