kris/afv-library
1
0
Fork 0
mirror of https://github.com/forcedotcom/afv-library.git synced 2026-07-30 03:09:50 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
a779945206
afv-library/skills/implementing-webapplication-agentforce-conversation-client/references/troubleshooting.md
k-j-kim a779945206
Rename webapp/webapplication to UI bundle in skills (#129) 
* Split generating-webapp-metadata into single-purpose skills

Extract the deployment sequence into a new deploying-webapp skill so each
webapp skill describes exactly one actionable goal. This improves agent
skill selection accuracy by eliminating multi-concern descriptions.

- generating-webapp-metadata: now focused on scaffolding, bundle config, CSP
- deploying-webapp: new skill for the 7-step deployment sequence

* Rename -webapp- skill directories and references to -webapplication-

Rename all 7 webapp skill directories to use the full "webapplication"
entity name. Update frontmatter name fields, cross-skill references,
and descriptive prose. Package names and CLI commands are preserved
as-is since those are actual identifiers.
2026-03-30 11:49:19 -05:00

1.5 KiB
Raw Blame History

Troubleshooting

Common issues when using the Agentforce Conversation Client.

Component throws "requires agentId"

Cause: agentId was not passed.

Solution: Pass agentId directly as a flat prop:

<AgentforceConversationClient agentId="0Xx000000000000AAA" />

Chat widget does not appear

Cause: Invalid agentId or inactive agent.

Solution:

  1. Confirm the id is correct (18-char Salesforce id, starts with 0Xx).
  2. Ensure the agent is Active in Setup → Agentforce Agents.
  3. Verify the agent is deployed to the target channel.

Authentication error on localhost

Cause: localhost:<PORT> is not trusted for inline frames.

Solution:

  1. Go to Setup → Session Settings → Trusted Domains for Inline Frames.
  2. Add localhost:<PORT> (example: localhost:3000).

Important:

  • This setting should be temporary for local development only.
  • Remove localhost:<PORT> from trusted domains after development.
  • Recommended: Test the Agentforce conversation client in a deployed app instead of relying on localhost trusted domains for extended periods.

Blank iframe / auth session issues

Possible cause: First-party Salesforce cookie restriction may block embedded auth flow in some environments.

Solution:

  1. Go to Setup → Session Settings.
  2. Find Require first party use of Salesforce cookies.
  3. Disable it only if needed and approved by your security/admin team.
  4. Save and reload.