Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Known Issue: F5 failed for Declarative Agents #12866

Open
Yimin-Jin opened this issue Dec 6, 2024 · 4 comments
Open

Known Issue: F5 failed for Declarative Agents #12866

Yimin-Jin opened this issue Dec 6, 2024 · 4 comments

Comments

@Yimin-Jin
Copy link
Contributor

Yimin-Jin commented Dec 6, 2024

Describe the bug
When you attempt to create a Declarative Agents template using the following steps, you may encounter a validation issue during the F5 process.

1. Create New App -> Agent -> Declarative Agent -> Add plugin -> Start with a new API -> * (any available template)
2. F5

you may encounter error messages in the console when pressing F5, with the following error:

(×) Error: teamsApp/extendToM365 failed.
(×) Error: Request failed with status code 400 (tracingId: 00-f6f5e6f56d4d8a738df5a3aceb94dd59-6a535aeadae6df11-01) 
BadRequest: Manifest package validations failed. 
Errors: Internal Error - Failed to make a successful HTTP request. Exception message: Response status code does not indicate success: 500 (Internal Server Error). 

Screenshots
image
Cause
This issue is caused by the deployment of new policies by Copilot, which restricts the use of certain keywords that may imply handling personal information, such as "person".

Workaround
As a temporary workaround, you can modify the instruction.txt file to avoid using the keyword "person" or any other keywords that might imply handling personal information.
You can use the following example template for your instruction.txt file:

You will assist the user in finding car repair records based on the information provided by the user. The user will provide relevant details, and you will need to understand the user's intent to retrieve the appropriate car repair records. You can only access and leverage the data from the 'repairPlugin' action.

VS Code Extension Information

  • Version [v5.10.1, v5.11.2024112909 (pre-release)]
Copy link
Contributor

Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.

@microsoft-github-policy-service microsoft-github-policy-service bot added the needs attention This issue needs the attention of a contributor. label Dec 6, 2024
@Nivedipa-MSFT
Copy link

@Yimin-Jin - Thank you for your inquiry! We have tested this on our end and did not encounter any errors. It is working fine for us. Could you please test it again and let us know if you still face the issue? If the issue persists, please share a reproduction video so we can raise a bug accordingly.

@Yimin-Jin
Copy link
Contributor Author

Yimin-Jin commented Dec 9, 2024

@Yimin-Jin - Thank you for your inquiry! We have tested this on our end and did not encounter any errors. It is working fine for us. Could you please test it again and let us know if you still face the issue? If the issue persists, please share a reproduction video so we can raise a bug accordingly.

@Nivedipa-MSFT - I apologize for the confusion in my previous description of the reproduction steps. The issue occurs only in the DA template with the API Plugin. The root cause is that the instruction.txt file does not comply with the latest security regulations.

@adashen adashen removed the needs attention This issue needs the attention of a contributor. label Dec 9, 2024
@Nivedipa-MSFT
Copy link

@Yimin-Jin - Could you please confirm if this issue has been resolved, or if you have any further query here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants