#support

API Response Issue After Agent Removal

TLDR sen.py shared an API response problem occurring after removing an agent. sojan_official asked them to log a GitHub issue for further investigation.

15mo

Join the chat

Sep 26, 2022 (15 months ago)

Photo of md5-9628d189658d8a84e88c1c15f6998082

sen.py

10:13 AM

Here's the Response of the API

json
{
  "payload": [
    {
      "id": 38,
    },
    {
      "id": 32,
    }
  ]
}

10:19

sen.py

10:19 AM

This happened after I removed the agent from the inbox, and presence.udpate keeps reporting that agent Online

Photo of md5-788237a2af5ff191b07ee9f215706ead

sojan_official

11:40 PM

could you log a github issue for the same. we will have someone from the team take a look

Sep 27, 2022 (15 months ago)

sen.py

04:36 AM

sojan_official Sure

04:54

sen.py

04:54 AM

https://github.com/chatwoot/chatwoot/issues/5502 - Bug report for any future reference

Chatwoot

Chatwoot | Knowledge Base powered by Struct.AI

Indexed 2221 threads (46% resolved)

Generate Knowledge

Similar Threads

Integrating Chatwoot Cloud into a Mobile App Using NodeJS

arkev. seeks assistance integrating Chatwoot cloud into an app via NodeJS, encountering 'Resource could not be found' errors. sojan_official suggests using client APIs and cross-verifying with browser requests. yousseff063 recommends Postman for testing. The issue remains unresolved.

Troubleshooting Agent Creation Error in Self-Hosted Chatwoot Server

LM10 had trouble creating an agent in a self-hosted Chatwoot server. sojan_official cleared the confusion by advising to use json payloads.

9mo

Issue with Interactive Messages Call Back Payload

no-1ne is having a problem with the payload of interactive messages and sought help by sharing a GitHub link.

8mo