You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/machine-learning/prompt-flow/how-to-troubleshoot-prompt-flow-deployment.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ You can either grant the endpoint identity **AzureML Data Scientist** on workspa
23
23
24
24
## Upstream request timeout issue when consuming the endpoint
25
25
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).
27
27
28
28
```yaml
29
29
request_settings:
@@ -51,7 +51,7 @@ For any other vulnerabilities of managed online deployments, Azure Machine Learn
51
51
52
52
## "MissingDriverProgram Error" or "Could not find driver program in the request"
53
53
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.
55
55
56
56
```text
57
57
'error':
@@ -106,20 +106,20 @@ inference_config:
106
106
107
107
Sometimes, you might notice that the deployment is taking too long to respond. There are several potential factors for this to occur.
108
108
109
-
- Model is not powerful enough (ex. use gpt over text-ada)
109
+
- Model is not powerful enough (example:use gpt over text-ada)
110
110
- Index query is not optimized and taking too long
111
111
- Flow has many steps to process
112
112
113
113
Consider optimizing the endpoint with above considerations to improve the performance of the model.
114
114
115
115
## Unable to fetch deployment schema
116
116
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:
118
118
119
119
:::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":::
120
120
121
121
- 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.
123
123
124
124
## Access denied to list workspace secret
125
125
@@ -128,4 +128,4 @@ If you encounter an error like "Access denied to list workspace secret", check w
128
128
## Next steps
129
129
130
130
- 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