Hi, one of the automations that always worked well behaves inconsistently now.
I receive such emails:
Automation「CHECK 100」 run failed
error message: Invalid prisma.space.findUnique() invocation: Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 9)
Also there are many runs on scheduler without any actions taken:
I haven’t changed anything in the automation for months so what could be the problem here?
Based on the error details you provided, we can see that the scheduling engine is successfully triggering your ‘CHECK 100’ automation as expected. The failure is occurring specifically at the database connection layer during execution.
The ‘connection pool timeout’ error indicates that your automation process is failing to acquire an available database connection within the allotted time. This is typically caused by the volume of concurrent requests exceeding the database’s connection pool capacity or Prisma configuration limits.
We recommend reviewing your database’s current connection limit and the concurrency settings within your Prisma setup to ensure they align with the volume of your automation tasks. It seems likely that an adjustment to your database’s connection pool size or query optimization would resolve this instability.
Automation「CHECK 100」 run failed