afv-library/skills/implementing-webapp-agentforce-conversation-client/references/troubleshooting.md
k-j-kim f39ac26c0d
Consolidate webapp skills @W-21338965@ (#118)
* Consolidate webapp skills into three focused skills

Merge 10 granular webapp skills into 3 consolidated skills:
- generating-webapp-ui: pages, components, layout, navigation, design
- generating-webapp-metadata: scaffolding, bundles, CSP, deployment
- generating-webapp-features: feature CLI (search, describe, install)

Keep standalone: implementing-webapp-file-upload,
implementing-webapp-agentforce-conversation-client (renamed from managing-),
using-webapp-salesforce-data.

Remove data visualization skill (not helpful).
Remove system-level instructions (a4drules refs, shell commands).
Incorporate Anthropic frontend-design skill content into UI skill.

* Fix frontmatter name to match directory for agentforce skill

---------

Co-authored-by: Hemant Singh Bisht <hsinghbisht@salesforce.com>
2026-03-27 22:34:44 +05:30

58 lines
1.5 KiB
Markdown

# 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:
```tsx
<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.