Shenanigans•2w ago

Error while fetching flow status

Hello, I recently encountered an error I can't quite make heads nor tails on. The following error below occurs after the myorgOrderC step around 5pm UTC in the attached flow.

{
    "error": "Internal: fetching flow status 01988ad7-aebb-89bd-c568-411502f6e9d5 while reporting true RawValue(<REDACTED>): pool timed out while waiting for an open connection @worker_flow.rs:273:14"
}

{
    "error": "Internal: fetching flow status 01988ad7-aebb-89bd-c568-411502f6e9d5 while reporting true RawValue(<REDACTED>): pool timed out while waiting for an open connection @worker_flow.rs:273:14"
}

Windmill Version: EE v1.520.0

worker-error-reprodu...

6 Replies

rubenf•2w ago

max_connections is likely too low for your db

ShenanigansOP•4d ago

I see, thank you very much. Hello @rubenf, sorry to bring this up again but we are still experiencing this issue. My team is using neon db with pooled connections. Is there a means to increase the connection timeout on windmill. There doesn't seem to be such an option in the postgresql resource

rubenf•4d ago

do not used pooled connection, use direct connections also would recommend not using neon for backing windmill, a local postgresql or rds would perform better

ShenanigansOP•4d ago

Thanks for the quick reply. I don't think i explained my problem well enough. We aren't self hosting windmill, we are on the team plan. My problem is related to using a pooled connection in a windmill flow. The flow has several scripts and failure steps that make queries to our neon db. Does using direct connections rather than pooled connections still apply in this case?

rubenf•4d ago

if you're seeing this error on the teams plan it's internal to us and you can just report the runs id here

ShenanigansOP•4d ago

An example runs ID is 0198bae7-a602-a5a2-34c1-e2e685497595. We appreciate your assistance on this issue

Error while fetching flow status

Did you find this page helpful?