Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Legal and regulatory considerations- Organizations need to evaluate potential specific legal and regulatory obligations when using any AI services and solutions, which may not be appropriate for use in every industry or scenario. Additionally, AI services or solutions are not designed for and may not be used in ways prohibited in applicable terms of service and relevant codes of conduct.
Some or all of this functionality is available as part of a preview release. The content and the functionality are subject to change.
Important
This feature uses services such as Bing and Azure Maps that transmit data—such as store location, latitude/longitude, and country/region code—outside your compliance boundary to obtain events, holidays, and weather information used to generate recommendations.
Your use of Bing is governed by the Microsoft Services Agreement and the Microsoft Privacy Statement. Noncommercial use limitations don't apply to products available for a fee through Microsoft volume license.
The Data Protection Addendum doesn't apply to your use of Bing within Microsoft Generative AI Services Previews.
This article describes how to diagnose and resolve issues with the Store Operations Agent.
Errors encountered during agent setup
Open button disabled after installing Store Operations Agent
After you install the Store Operations Agent in Copilot Studio, the dialog indicates "Installed", but the Open button is disabled. This issue occurs because the agent is completing background provisioning (flows, connections, Dataverse setup).
Resolution:
Wait a short time. The Open button is automatically enabled after setup finishes successfully. If it remains disabled, close the dialog, refresh Copilot Studio, and open the agent directly from the Agents list.
Caution
This behavior is expected during initial setup. Avoid reinstalling the agent while provisioning is in progress.
ConnectionNotSet error
After you create a connector, you might immediately see a ConnectionNotSet error even when the connection is valid. This error is due to an intermittent sync delay and doesn't indicate a broken connection.
Resolution:
Wait 30–60 seconds, refresh the page, and try again. The error usually resolves automatically.
Error when publishing the agent
Publishing the Store Operations Agent can fail with an error that indicates issues with one or more topics. This error typically occurs when a required flow in the managed agent is disabled or uses an invalid connection reference.
Resolution:
To resolve this error, update the connection references in the affected flows:
In Copilot Studio, open the Store Operations Agent, and then select Flows in the left navigation.
Find and open the
SendStoreSnapshotEmailflow.
On the Manage tab, update the connection reference.
Change the connection from Provided by run-only user to an explicitly created connection. Save the changes, and then turn on the flow.
Return to the Agent tab, refresh the browser, and wait 15–20 seconds for the changes to sync.
Publish the agent again.
SystemError during agent interaction
When you interact with the Store Operations Agent, you might see a generic SystemError message - "Sorry, something went wrong. Error code: SystemError". This error typically indicates a backend or configuration issue that can't be resolved from the client experience alone.
Resolution:
Verify that the Store Operations Agent is successfully published in Copilot Studio. Refresh the browser and retry the interaction after a few minutes to rule out transient platform issues.
Note
SystemError messages don't indicate a user action issue. They require backend or configuration validation and may need support-assisted remediation.
Publish button not enabled
In Copilot Studio, the Publish option is disabled and a banner appears stating, "This feature isn’t available until your agent has finished setting up." This issue typically occurs immediately after you install the Store Operations Agent, or when background setup doesn't complete successfully.
The Store Operations Agent is a Microsoft-managed solution. During installation, Copilot Studio performs asynchronous setup tasks, such as provisioning Dataverse components, validating connections, and configuring managed flows. This message doesn't indicate a user error. It reflects that agent provisioning is still in progress or incomplete and until setup completes successfully, publishing and some configuration actions remain unavailable.
Resolution:
Wait a few minutes after installation to allow background setup to complete. Refresh the Copilot Studio page and reopen the agent. Verify that the agent appears without setup warnings in the Agents list. Check that the required flows are enabled and the connection references are valid.
If the banner persists for an extended period, reopen the environment and agent in Copilot Studio. Confirm that the managed solution installation completed without errors.
Note
Publishing becomes available automatically after setup finishes successfully.
Agent fails to open in Microsoft Teams
After you publish the Store Operations Agent through the Show to everyone in my org section, the Teams app must be approved in the Teams admin center. Even after admin approval, users might find that the app fails to load or doesn't open as expected in Microsoft Teams.
This issue can occur if the agent isn't ready for Teams consumption due to one or more of the following reasons:
- Microsoft Teams app propagation is still in progress after approval (tenant-wide availability is asynchronous).
- The agent configuration changed after publishing and requires republish to Teams.
- The Teams client is caching an older version of the app configuration.
Resolution:
To resolve this error, use the following checklist to verify common causes:
In Copilot Studio, open the Store Operations Agent and verify successful publish.
Check whether any configuration changes were made after the initial publish. If changes were made, republish the agent in Copilot Studio.
In Microsoft Teams:
- Sign out and sign back in, or clear the Teams cache.
- Ensure users open the agent from the Apps section (not a previously pinned or cached app).
Allow time for Teams app propagation after admin approval. In some cases, availability might take additional time to reflect across the organization.
Note
Teams app approval and visibility don't always guarantee immediate usability. Always republish the agent after configuration changes and allow for propagation before troubleshooting further.
Additional support and troubleshooting guidance
For unresolved issues or when the root cause is unclear, refer to the broader Microsoft Copilot Studio troubleshooting guidance, which covers common platform errors, agent setup issues, publishing problems, and runtime failures.
If any issue persists even after you complete the resolution steps given, contact Microsoft Store Operations Agent support. Include the Conversation ID, timestamp, and environment details (if available) shown in the error message to help with further investigation.
Common challenges and mitigations
The following list highlights common challenges and recommended actions to mitigate them.
The agent doesn't recognize user jargon
Mitigation: Add common user terms to the agent by using trigger phrases or a synonyms list, if available. Also include these terms in the agent description so the orchestrator can route queries more effectively.
The agent provides incorrect responses
Mitigation: AI-generated responses might be incorrect when the model doesn't have sufficiently grounded data. Provide explicit fallback responses (for example, "I don't have that information") when the knowledge source doesn't contain an answer. Instruct the agent to respond only with validated product data. Although Copilot Studio limits fine-grained tuning beyond knowledge linking, comprehensive, high-quality grounding data can significantly reduce incorrect answers. Review conversational boosting settings to determine whether they're contributing to incorrect answers. In some cases, you can disable them.
The agent can't reliably handle multi-part or complex requests
Mitigation: For multi-part queries (for example, "Show me today's low-stock items and create a replenishment request"), the agent might address only one part of the request. Configure the agent to detect multi-part requests and prompt the user to handle each part sequentially. For example: "Let's handle one task at a time. First, I'll list today's low-stock items." After the user confirms, proceed to the next task.
The agent encounters integration failures with dataflows or connectors
Mitigation: Integration failures, such as expired credentials, can prevent the agent from accessing updated data. Configure monitoring and alerts for failed dataflow runs in Power Platform, and consider using a Power Automate flow to send notifications. Establish a documented process to renew or update connector credentials when they expire.
Support
Contact Microsoft Support for technical issues that can't be resolved locally, such as the agent not appearing after 48 hours or suspected Copilot Studio issues. For newly deployed agents, also contact your Microsoft Technical Account Manager or Premier Support. Include the environment ID, agent ID, and relevant timestamps when you open a ticket.
Join the Power Platform Community forums or the Microsoft Tech Community for Copilot Studio. Preview users and Microsoft engineers frequently discuss issues (for example, "agent not publishing" or "data source connection") and share workarounds. Because Copilot Studio is evolving, monitoring community discussions can help you stay informed about known issues and updates.