Skip to content

invalid_param error with ConversationsClient.search api #509

@c-semaan

Description

@c-semaan

Hello,

This week, we started getting errors with the node client and we're unable to identify the issue. It is happening after adding the starting_after param which we get from data.response?.pages?.next?.starting_after.

Tested on 6.0.0 and 7.0.1 client version.

Search arguments.

   query: {
      "operator": "AND",
      "value": [
        {
          "field": "created_at",
          "operator": ">",
          "value": "1769421845"
        },
        {
          "field": "created_at",
          "operator": "<",
          "value": "1769681045"
        }
      ]
    }
    pagination: {
      "per_page": 150,
      "starting_after": "WzE3Njk1NzY2ODkwMDAsMjE1NDcyODU2NDQ4NjQ2LDNd"
    }

Error caught:

{
  statusCode: undefined,
  body: undefined,
  rawResponse: {
    headers: {
    },
    redirected: false,
    status: 0,
    statusText: "Unknown Error",
    type: "error",
    url: "",
  },
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions