Skip to content

Commit 321b111

Browse files
likebuptlgayhardt
andauthored
Apply suggestions from code review
Co-authored-by: Lauryn Gayhardt <[email protected]>
1 parent a800af6 commit 321b111

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/machine-learning/prompt-flow/how-to-troubleshoot-prompt-flow-deployment.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ You can either grant the endpoint identity **AzureML Data Scientist** on workspa
2323

2424
## Upstream request timeout issue when consuming the endpoint
2525

26-
If you use CLI or SDK to deploy the flow, you may encounter timeout error. By default the `request_timeout_ms` is 5000. You can specify at max to 5 minutes, which is 300000 ms. Following is example showing how to specify request time out in the deployment yaml file. Learn more about the deployment schema [here](../reference-yaml-deployment-managed-online.md).
26+
If you use CLI or SDK to deploy the flow, you may encounter timeout error. By default the `request_timeout_ms` is 5000. You can specify at max to 5 minutes, which is 300000 ms. Following is example showing how to specify request time out in the deployment yaml file. To learn more, see [deployment schema](../reference-yaml-deployment-managed-online.md).
2727

2828
```yaml
2929
request_settings:
@@ -51,7 +51,7 @@ For any other vulnerabilities of managed online deployments, Azure Machine Learn
5151

5252
## "MissingDriverProgram Error" or "Could not find driver program in the request"
5353

54-
If you deploy your flow encounter the following error, it might be related to the deployment environment.
54+
If you deploy your flow and encounter the following error, it might be related to the deployment environment.
5555

5656
```text
5757
'error':
@@ -106,20 +106,20 @@ inference_config:
106106

107107
Sometimes, you might notice that the deployment is taking too long to respond. There are several potential factors for this to occur.
108108

109-
- Model is not powerful enough (ex. use gpt over text-ada)
109+
- Model is not powerful enough (example: use gpt over text-ada)
110110
- Index query is not optimized and taking too long
111111
- Flow has many steps to process
112112

113113
Consider optimizing the endpoint with above considerations to improve the performance of the model.
114114

115115
## Unable to fetch deployment schema
116116

117-
After you deploy the endpoint and want to test it in the **Test tab** in the endpoint detail page, if the **Test tab** shows **Unable to fetch deployment schema** like following, you can try the following 2 methods to mitigate this issue:
117+
After you deploy the endpoint and want to test it in the **Test tab** in the endpoint detail page, if the **Test tab** shows **Unable to fetch deployment schema**, you can try the following two methods to mitigate this issue:
118118

119119
:::image type="content" source="./media/how-to-deploy-for-real-time-inference/unable-to-fetch-deployment-schema.png" alt-text="Screenshot of the error unable to fetch deployment schema in Test tab in endpoint detail page. " lightbox = "./media/how-to-deploy-for-real-time-inference/unable-to-fetch-deployment-schema.png":::
120120

121121
- Make sure you have granted the correct permission to the endpoint identity. Learn more about [how to grant permission to the endpoint identity](how-to-deploy-for-real-time-inference.md#grant-permissions-to-the-endpoint).
122-
- It might be because you ran your flow in an old version runtime and then deployed the flow, the deployment used the environment of the runtime which was in old version as well. Update the runtime following [this guidance](./how-to-create-manage-runtime.md#update-a-runtime-on-the-ui) and rerun the flow in the latest runtime and then deploy the flow again.
122+
- It might be because you ran your flow in an old version runtime and then deployed the flow, the deployment used the environment of the runtime which was in old version as well. To update the runtime, follow [Update a runtime on the UI](./how-to-create-manage-runtime.md#update-a-runtime-on-the-ui) and rerun the flow in the latest runtime and then deploy the flow again.
123123

124124
## Access denied to list workspace secret
125125

@@ -128,4 +128,4 @@ If you encounter an error like "Access denied to list workspace secret", check w
128128
## Next steps
129129

130130
- Learn more about [managed online endpoint schema](../reference-yaml-endpoint-online.md) and [managed online deployment schema](../reference-yaml-deployment-managed-online.md).
131-
- - Learn more about how to [troubleshoot managed online endpoints](../how-to-troubleshoot-online-endpoints.md).
131+
- Learn more about how to [troubleshoot managed online endpoints](../how-to-troubleshoot-online-endpoints.md).

0 commit comments

Comments
 (0)