Simultaneous Cron Triggers possibly causing Hyperdrive persistent errors
Hi, I'm getting a
I'm creating the database connection inside the scheduled function, which I assume results in two separate connections for both cron calls. After this error occurs on one trigger, the other one also starts failing. Even simple
Is there anything I can do to prevent this from happening? I'm not entirely sure why this occurs, since sometimes both jobs run as expected without any issues.
For more context, I'm using Drizzle as the ORM, Neon as the database, and Hyperdrive for connection pooling. My Hyperdrive and connection setup follows the documentation.
write CONNECTION_CLOSED <HYPERDRIVE_ID>.hyperdrive.local:5432*/20 * * * *0 * * * *I'm creating the database connection inside the scheduled function, which I assume results in two separate connections for both cron calls. After this error occurs on one trigger, the other one also starts failing. Even simple
SELECTIs there anything I can do to prevent this from happening? I'm not entirely sure why this occurs, since sometimes both jobs run as expected without any issues.
For more context, I'm using Drizzle as the ORM, Neon as the database, and Hyperdrive for connection pooling. My Hyperdrive and connection setup follows the documentation.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,529Members
Resources
Similar Threads
Was this page helpful?
