Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 14 additions & 1 deletion CenterofExcellenceCoreComponents/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -83,10 +83,20 @@ This solution contains the core components for the CoE Starter Kit, including in

### Inventory and Sync Issues

- **[Flow Performance and Long Runtimes](./TROUBLESHOOTING-FLOW-PERFORMANCE.md)** - Guide for resolving issues where sync flows take 7+ hours to complete
- **[PVA/Copilot Studio Sync Issues](./TROUBLESHOOTING-PVA-SYNC.md)** - Guide for resolving issues where not all bots appear in the inventory

### Common Questions

**Q: Why are my sync flows taking 7+ hours to complete?**

A: This is typically caused by API throttling when multiple flows run concurrently. To resolve:
1. Set `admin_DelayObjectInventory` to `Yes`
2. Verify `admin_DelayInventory` is set to `Yes`
3. Ensure `admin_FullInventory` is set to `No` (for regular runs)

The delay settings spread API calls over time, preventing throttling and reducing runtime to 30-120 minutes. See the **[Flow Performance Troubleshooting Guide](./TROUBLESHOOTING-FLOW-PERFORMANCE.md)** for detailed resolution steps.

**Q: Why aren't all my resources showing up in the inventory?**

A: The inventory flows run in incremental mode by default, which only syncs new or recently modified resources. To capture all resources, you need to run a full inventory by setting the `admin_FullInventory` environment variable to `Yes`. Remember to set it back to `No` after the full inventory completes.
Expand All @@ -105,7 +115,10 @@ Key environment variables that control inventory behavior:

- `admin_FullInventory` - Run full inventory (Yes/No, default: No)
- `admin_InventoryFilter_DaysToLookBack` - Days to look back for modified resources (default: 7)
- `admin_DelayObjectInventory` - Add random delay to avoid throttling (Yes/No, default: No)
- `admin_DelayObjectInventory` - Add delay to prevent API throttling (Yes/No, default: Yes) - **Recommended: Keep enabled**
- `admin_DelayInventory` - Add delay for Dataverse health (Yes/No, default: Yes) - **Recommended: Keep enabled**

**⚠️ Important**: Keep delay variables enabled to prevent flow performance issues. See the **[Flow Performance Troubleshooting Guide](./TROUBLESHOOTING-FLOW-PERFORMANCE.md)** for details.

## Additional Documentation

Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
<environmentvariabledefinition schemaname="admin_DelayObjectInventory">
<defaultvalue>no</defaultvalue>
<description default="Inventory - If Yes, will run a delay step to assist with the Dataverse throttling. Things like solutions, apps, flows, will have delays in the individual envt runs. Default No.">
<label description="Inventory - If Yes, will run a delay step to assist with the Dataverse throttling. Things like solutions, apps, flows, will have delays in the individual envt runs. Default No." languagecode="1033" />
<defaultvalue>yes</defaultvalue>
<description default="Inventory - If Yes, will run a delay step to assist with the Dataverse throttling. Things like solutions, apps, flows, will have delays in the individual envt runs. Default Yes. Recommended to keep enabled to prevent API throttling on concurrent flow executions.">
<label description="Inventory - If Yes, will run a delay step to assist with the Dataverse throttling. Things like solutions, apps, flows, will have delays in the individual envt runs. Default Yes. Recommended to keep enabled to prevent API throttling on concurrent flow executions." languagecode="1033" />
</description>
<displayname default="DelayObjectInventory">
<label description="DelayObjectInventory" languagecode="1033" />
Expand Down
Loading