Diagnose Marketing Agent Errors

1. Takes the user's symptom and starts discovery. The symptoms include a campaign brief that always shows "No Brand Found", a Campaign Creation agent that fails when it saves campaigns, and a "business unit not set" error in a campaign agent copied to a playground org.
2. Inspects the agent setup. It finds that the agent uses standard managed-package actions and a legacy Bot. It queries both orgs to compare packages, flows and Marketing Cloud configuration.
3. Tries changes and redeploys. It redeploys the Agent Script bundle and revises its instructions several times. It deploys a Record Type fix to several profiles, though that fix did not address the actual error.
4. Pins down the root cause. Examples from the evidence:

• A brand that existed in CMS but was not the default in Content Workspace settings.
• A Brief object with no BusinessUnitId field on the playground org, because Marketing Cloud Engagement is not fully provisioned there.
• A misleading error: the create step succeeded and the Campaign record was saved, but a later save call in the managed action failed.

1. Where the fix needs a manual UI change or a platform configuration change, writes a plan and pauses.

For building these agents rather than repairing them, see Build Marketing Campaign Agents.