Description
The PowerShield | Sync Connectors flow (part of the managed Copilot Agent Kit / Power CAT Copilot Studio Kit solution) fails in the Upsert Connector Actions step (Custom API cat_UpsertConnectorActions), inside the Collection Active Connectors Apply-to-each loop, with the following error:
UpsertConnectorActionsAction failed: A validation error occurred. The length of the 'cat_connectoractionname' attribute of the 'cat_connectoraction' entity exceeded the maximum allowed length of '100'.
Run details
The run started Jul 16, ~12:47 PM, ran for 00:33:47, and failed on iteration 6 of 1588 items in the loop. The triggering connector is mcp_Governance — one of its action names exceeds 100 characters. Connector action name values are pulled from raw connector metadata via an HTTP call and stringified via a Compose step, and there is no truncation logic in the flow before the upsert.
Additional investigation
I checked the cat_connectoraction table schema in the solution. The cat_connectoractionname field is the table's primary column but is not marked Required, and the table has no alternate keys defined. There is a separate cat_actionkey field (Required: Yes, e.g. Contact_PutValue) that appears to be the actual identifier used for matching/dedup, rather than the Name field.
This suggests the Name field isn't used for matching, so truncating it would likely be low-risk functionally (mainly cosmetic — the full name would get cut off in the Dataverse UI) rather than causing incorrect record matching. That said, I'll leave the exact fix to the maintainers' judgment, since there are a couple of reasonable approaches: truncating the connector action name to 100 characters in the flow before the upsert, or increasing the max length of the cat_connectoractionname column in Dataverse.
Precedent
This looks like the same category of issue as #321 (a different field, cat_description/cat_agentdetails, exceeding a 2000-character Dataverse limit during automated sync), which was acknowledged and fixed, shipping in the CopilotStudioAccelerator-October2025 release.
Screenshots
Description
The PowerShield | Sync Connectors flow (part of the managed Copilot Agent Kit / Power CAT Copilot Studio Kit solution) fails in the Upsert Connector Actions step (Custom API
cat_UpsertConnectorActions), inside the Collection Active Connectors Apply-to-each loop, with the following error:Run details
The run started Jul 16, ~12:47 PM, ran for 00:33:47, and failed on iteration 6 of 1588 items in the loop. The triggering connector is mcp_Governance — one of its action names exceeds 100 characters. Connector action name values are pulled from raw connector metadata via an HTTP call and stringified via a Compose step, and there is no truncation logic in the flow before the upsert.
Additional investigation
I checked the
cat_connectoractiontable schema in the solution. Thecat_connectoractionnamefield is the table's primary column but is not marked Required, and the table has no alternate keys defined. There is a separatecat_actionkeyfield (Required: Yes, e.g.Contact_PutValue) that appears to be the actual identifier used for matching/dedup, rather than the Name field.This suggests the Name field isn't used for matching, so truncating it would likely be low-risk functionally (mainly cosmetic — the full name would get cut off in the Dataverse UI) rather than causing incorrect record matching. That said, I'll leave the exact fix to the maintainers' judgment, since there are a couple of reasonable approaches: truncating the connector action name to 100 characters in the flow before the upsert, or increasing the max length of the
cat_connectoractionnamecolumn in Dataverse.Precedent
This looks like the same category of issue as #321 (a different field,
cat_description/cat_agentdetails, exceeding a 2000-character Dataverse limit during automated sync), which was acknowledged and fixed, shipping in theCopilotStudioAccelerator-October2025release.Screenshots