Provisioning of declarative agent does not update the current angent

[TheZalRevolt]

Describe the bug
Today (01/31/2025) the provisioning of an existing declarative agent stopped working even if the logs declare a success in the operation of provisioning.

To Reproduce
Steps to reproduce the behavior:

1. Open visual studio code
2. Made a change (I changed the name of the agent and the instruction inside instruction.txt file)
3. Click on provisioning
4. The change aren't made in the provisioned agent.

Expected behavior
In the Copilot Panel I should be able to see the changes like the name.

VS Code Extension Information (please complete the following information):

• OS: Windows 11
• Version v5.12.1

Additional context
This is the provisioning log:

Screen of the DeclarativeAgent.json file

Screen of the copilot page

[teams-toolkit-assistant]

👋 Hi @TheZalRevolt,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 2 business days

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

Based on your description, it seems that although the provisioning process completes successfully, the changes are not reflected in the Copilot Panel. This issue has been reported by multiple users and is often related to delays in the backend services updating the agent.

Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Wait for Backend Updates:

   • It's possible that there is a delay in the backend services updating the agent. Users have reported that changes sometimes take a few hours to appear. Please wait for a few hours and check if the changes are reflected.

2. Retry Provisioning:

   • Try provisioning the agent again. Sometimes, retrying the process can help in ensuring that the changes are updated correctly.

3. Check for Any Outages:

   • Occasionally, external dependencies or services might be experiencing outages. Check the Microsoft Service Health Dashboard to see if there are any reported issues.

4. Review Logs for Any Hidden Errors:

   • Although the logs indicate a successful provisioning, there might be minor warnings or hidden errors. Carefully review the logs for any warnings or messages that might indicate a problem.

5. Escalate the Issue:

   • If the issue persists, you can escalate it by providing detailed information, including your Microsoft account details, to the Teams Toolkit support team for further investigation.

6. Consult the Documentation:

   • Refer to the Teams Toolkit Documentation for any updates or changes in the provisioning process.

For a similar issue, you can refer to the GitHub issue reported here.

Actionable Steps:

1. Retry the provisioning process and check for updates after a few hours.
2. If the issue persists, provide detailed information, including Microsoft account details, to the support team for further internal investigation.

If you have any further questions or need additional assistance, please let me know!

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[huimiu]

Hi @TheZalRevolt, thanks for reaching out. Sometimes, agent provision success doesn't take effect immediately. Could you please refresh the Copilot page after a while and check again?

Also, please make sure that the account logged into Teams Toolkit is the same as the one logged into the browser.

[TheZalRevolt]

On VSCode I am using these accounts

On my copilot page I am logged in with the first one on the image up there

Last time I waited for like an hour and got no result

EDIT:
I found a workaround for this problem. Uninstalling the agent and provision it again allows me to see the new agent

[huimiu]

Thanks for sharing this! We'll find the root cause of this issue.

[huimiu]

Hi @TheZalRevolt, there is a known issue where the agent update is delayed because the update API is asynchronous. Currently, when the agent updates, it shows as successful, but it hasn't actually updated.

We understand that it's frustrating when the agent hasn't updated even after an hour. We're working with our partner team to improve this experience.
CC. @MuyangAmigo @anchenyi

[TheZalRevolt]

@huimiu Thanks!