test user

I implemented APP to update visitor information once chat is opened.

It worked in my environment but it sometimes fails to update some field in some customers environment. Not sure what's the conditions..

Here is the source code:

client.set({
  'visitor.name': 'aaa',
  'visitor.email': 'bbb',
  'visitor.phone': 'ccc',
  'visitor.notes': 'ddd'
 }).then(function (result) {
   console.log('result：' + JSON.stringify(result));
 });

Here is sample error:

{
   "errors":{
      "visitor.name":{
         "id":"13221074.1CClGKVmCEMmTJx",
         "__status":"failed",
         "path":"visitor.name"
      },
      "visitor.phone":{
         "id":"13221074.1CClGKVmCEMmTJx",
         "__status":"failed",
         "path":"visitor.phone"
      }
   },
   "visitor.notes":"ddd",
   "visitor.email":"bbb"
}

The fields which is failed to update are not fixed.

Sometimes only notes, sometimes success.

 

Before calling client.set(), APP calls client.get(visitor) to fetch visitor's information and 100% success, which means client itself works correctly.

Kindly give me some advice to avoid the errors.

Thank you

Hi Eric,

Thank you for your suggestion.

Even though I added the httpCompleteResponse parameter, response header doesn't include X-Rate-Limit nor X-Rate-Limit-Remaining.

Do you have any idea about this problem?

 

Source code

var options = {
    url: '/api/v2/deleted_users/' + userId,
    type: 'DELETE',
    dataType: 'json',
    contentType: 'application/json',
    httpCompleteResponse: true
};

Response

Permanently Delete User endpoint doesn't return response in my App.

Once API call hit rate limit which is 700 call per 10 mins, there is error in console.

However the App couldn't get responses nor any errors.

Does anyone has any ideas to deal with status 429 errors in Apps?

This error happens only when the app runs simultaneously by several users.

This is rare case though, I'd like to show "Too many request" error message on UI at least.

Thank you in advance.

 

Here is source code which has a problem.

var options = {
    url: '/api/v2/deleted_users/' + userId,
    type: 'DELETE',
    dataType: 'json',
    contentType: 'application/json',
};

try {
  return client.request(options).then(
    function (data) {
      console.error(data);
      return data;
    },
    function (error) {
      console.error(error);
      return error;
    }
  );
} catch (e) {
  console.error(e);
}

Hi Tipene,

Thanks for your reply.

I understood your suggestion is the best option.

Yusuke

Hello team,

I'm trying to implement an app to show soft deleted users and to delete them permanently.

 

Endpoint below returns results include permanently deleted user:

GET /api/v2/deleted_users

If I exclude users whose name are "Permanently Deleted User", I can get soft deleted users list though, there are 2 problems.

1. Renaming to "Permanently Deleted User" takes time after permanent deletion, which cause my app still display permanently deleted users as soft deleted users until the name will be changed.

2. My customer who will use this app need to delete thousands of users per week. The number of permanently deleted users will be accumulated, which means more time and API credit are required to get soft deleted users from result of the endpoint above.

 

I wondered that no particular API to get soft deleted users even though there is admin UI to see them.

Any help would be appreciated.

Best regards,

Yusuke

Hi Ayush,

The email is no longer supported. Could you tell me other method to share my account?

Best Regards,

Tokutoku

zChat.removeTags didn't work in my custom Chat Widget.

It seems issue of Agent Workspace.

Flow

1. Add Tag and start chat → A ticket with "zopim_chat" and "test_tag" tag will be created.

zChat.addTag(['test_tag'])

2. Finish chat by zChat.endChat()

3. Reload browser and initialize chat widget

constructor() {
  zChat.removeTags(['test_tag'])
}

4. Start chat without adding tag

→ A new ticket with "zopim_chat" and "test_tag" tag will be created.

Conditions

 - Using Agent Workspace

 - Start chat again in a short time from same browser (Not same session? but something is same)