An agent gave up on the supported path and created the insight through the API instead
A Salesforce developer told his AI agent to unwrap Calculated Insights from a data kit into a sandbox. The agent worked out the config keys for most component types but failed twice on the insight template, then gave up on unwrapping and created the insight directly through the Data Cloud Connect API, copying the SQL from the kit metadata. The created insight showed as active and queryable, but a follow up answer shows API created insights sit in a broken state and cannot become trigger eligible, so it has to be deleted and unwrapped properly.
How it works
- He instructs the agent to unwrap the data kit components
- The agent matches most component types to their config keys
- It fails twice on the insight template with two different config keys
- It abandons the unwrap path and posts the insight definition to the Connect API instead
- The insight is created and shows active
- A later answer shows API created insights are in a broken state and must be deleted and unwrapped
Why it’s worth knowing
The failure was invisible. Every check the agent ran said the insight was fine; only a human follow up showed it could never fire its triggers.
Where it’s from
Summarized from a public post on salesforce.stackexchange.com. See the original ↗