Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Evolution API 2.3.7 + Chatwoot latest: PrismaClientValidationError (Invalid Date) when sending messages

Open
#2,667 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker-compose, postgresql, redis, typescript
Domain
api, backend, databases

Research direction

No source file or test is named. Start at the outgoing-message path that builds the Prisma query for jidOptions and updatedAt while handling @lid and remoteJidAlt, then reproduce the failure from a Chatwoot reply. Done means the query receives a valid date and the message is delivered without PrismaClientValidationError.

Written by the indexing model from the issue text.

Description

bug
Welcome!
  • Yes, I have searched for similar issues on GitHub and found none.
What did you do?

Environment

  • Evolution API: 2.3.7
  • Chatwoot: latest (Docker)
  • PostgreSQL: 15
  • Redis: 7
  • Docker Compose
  • WhatsApp connected successfully

Problem

Incoming WhatsApp messages are delivered correctly to Chatwoot.

However, replying from Chatwoot fails.

The message is never sent to WhatsApp.

Error

PrismaClientValidationError

Invalid value for argument gte:

Provided Date object is invalid.

Expected Date.

The generated query contains:

where: {
  OR: [
    {
      jidOptions: {
        contains: "104234762670201@lid"
      }
    }
  ],
  updatedAt: {
    gte: new Date("Invalid Date")
  }
}

What works

  • WhatsApp connection ✅
  • Incoming messages ✅
  • Contacts sync ✅

What fails

  • Sending messages from Chatwoot to WhatsApp ❌

Additional information

The issue still happens after updating Evolution API to version 2.3.7.

The instance already supports remoteJidAlt for @lid, but Prisma still generates an Invalid Date in the query.

Any guidance would be appreciated.

What did you expect?

I expected Chatwoot to send the WhatsApp message successfully through Evolution API.

Incoming messages already work correctly.

The reply should be delivered to WhatsApp without generating any Prisma validation errors.

What did you observe instead of what you expected?

Instead of sending the message, Evolution API returns a PrismaClientValidationError.

The generated query contains:

updatedAt: {
gte: new Date("Invalid Date")
}

Incoming messages continue to work, but every outgoing message from Chatwoot fails.

Screenshots/Videos

I can provide screenshots of the Prisma error, Docker environment and Chatwoot configuration if needed.

Which version of the API are you using?

2.3.7

What is your environment?

Linux

Other environment specifications

Docker Compose
Evolution API 2.3.7
Chatwoot latest
PostgreSQL 15
Redis 7
Hosted on Vultr VPS

Issue only affects outgoing messages from Chatwoot.
Incoming messages work correctly.

If applicable, paste the log output

PrismaClientValidationError

Invalid value for argument gte:
Provided Date object is invalid.
Expected Date.

where: {
OR: [
{
jidOptions: {
contains: "104234762670201@lid"
}
}
],
updatedAt: {
gte: new Date("Invalid Date")
}
}

Additional Notes

I can provide Docker Compose configuration, Evolution API configuration and additional logs if needed.

I am available to test patches or beta fixes.

Dominant language
TypeScript
Stars
9.6k
Forks
7.3k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from evolution-foundation/evolution-api

All issues in evolution-foundation/evolution-api

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.