Repository navigation
Error in "Deploy and monitor a model in Azure Machine Learning" – Retrain model on prod data from a pull request comment #50
Description
Issue: Error in "Retrain the model on prod data from a pull request comment"
Description
While executing the workflow, the process fails during metrics extraction and pull request commenting. Accuracy and AUC values are not generated, and a 403 error (Resource not accessible by integration) occurs when attempting to post results as a PR comment. Due to this failure, model training does not complete and no models or related resources are created.
Task
Retrain the model on prod data from a pull request comment
Steps
- Extract production metrics from logs
- Post extracted metrics as a pull request comment
Expected Behavior
- Accuracy and AUC values should be successfully extracted and displayed
- Metrics should be posted as a PR comment without errors
- Workflow should complete successfully
- Model and related resources should be created
Actual Behavior
- Accuracy and AUC values are not appearing
- 403 error occurs while commenting on PR (
Resource not accessible by integration) - Workflow fails and does not complete
- Models and related resources are not created
Screenshot:
Activity
[-]Error in "Retrain the model on prod data from a pull request comment"[/-][+]Error in "Deploy and monitor a model in Azure Machine Learning" – Retrain model on prod data from a pull request comment[/+]umairXtreme commentedon Apr 16, 2026
Hi I'm facing the same issue.
v-vfarias commentedon Apr 17, 2026
Hi @ehtishamanwar1122 and @umairXtreme, we are having a look at the issue and will be updating this thread accordingly. Thanks for the report.
umairXtreme commentedon May 21, 2026
@v-vfarias any update on this please?
v-vfarias commentedon May 25, 2026
As I have tested, I have reproduced the issue. The problem is related to the permissions on the .github/workflows/train-prod.yml, you might need to add under permissions, right bellow issues: write add pull-request: write. Let me know if the issue persist.
ehtishamanwar1122 commentedon Jun 16, 2026
Yes, the previous issue was resolved using this method. However, another issue appeared in the next task. I have opened a new issue for it, please look into it.