Wait node does not complete

The WAIT node does not work, when the trigger time arrives, nothing happens and the flow does not go further. Tried it on 2 different servers and two different versions of n8n

The screenshot shows that the response time has come a long time ago, but nothing went further. There are examples where more than 2 days, there is also no progress

wait does not complete

  • n8n version: 1.11.0 and 0.231
  • Database: Postgres
  • n8n EXECUTIONS_PROCESS setting: main
  • Running n8n via: docker
  • Operating system: debian 12

config:
version: “3.8”

x-shared: &shared
restart: always
environment:
- N8N_HOST=${SUBDOMAIN}.${DOMAIN_NAME}
- N8N_PORT=5678
- N8N_PROTOCOL=https
- NODE_ENV=production
- WEBHOOK_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/
- GENERIC_TIMEZONE=${GENERIC_TIMEZONE}
- NODE_FUNCTION_ALLOW_BUILTIN
- NODE_FUNCTION_ALLOW_EXTERNAL
- N8N_ENCRYPTION_KEY
- N8N_PUSH_BACKEND=sse
# ------ redis ------ #
- QUEUE_BULL_REDIS_HOST
- QUEUE_BULL_REDIS_PORT
# - QUEUE_BULL_REDIS_USERNAME
- QUEUE_BULL_REDIS_PASSWORD
- QUEUE_BULL_REDIS_DB
# ----- postgres ----- #
- DB_TYPE=postgresdb
- DB_POSTGRESDB_HOST
- DB_POSTGRESDB_PORT
- DB_POSTGRESDB_DATABASE
- DB_POSTGRESDB_USER
- DB_POSTGRESDB_PASSWORD
# ----- logging ----- #
- N8N_LOG_OUTPUT=console,file
- N8N_LOG_LEVEL=debug
# ----- scaling ----- #
- EXECUTIONS_MODE
- EXECUTIONS_PROCESS
- EXECUTIONS_TIMEOUT
- EXECUTIONS_DATA_PRUNE
- EXECUTIONS_DATA_MAX_AGE
- EXECUTIONS_DATA_PRUNE_TIMEOUT
# - N8N_DISABLE_PRODUCTION_MAIN_PROCESS=true
# ----- SMTP ----- #
# - N8N_EMAIL_MODE
# - N8N_SMTP_HOST
# - N8N_SMTP_PORT
# - N8N_SMTP_USER
# - N8N_SMTP_SENDER
# - N8N_SMTP_PASS
volumes:
- n8n:/home/node/

services:
n8n-postgres:
image: postgres:${POSTGRES_VERSION}
restart: always
environment:
POSTGRES_USER: ${DB_POSTGRESDB_USER}
POSTGRES_PASSWORD: ${DB_POSTGRESDB_PASSWORD}
POSTGRES_DB: ${DB_POSTGRESDB_DATABASE}
volumes:
- n8n-postgres:/var/lib/postgresql/data
ports:
- “0.0.0.0:5432:5432”
n8n-redis:
image: redis:${REDIS_VERSION}
restart: always
ports:
- ‘0.0.0.0:6379:6379’
command: redis-server --save 20 1 --loglevel warning --requirepass ${QUEUE_BULL_REDIS_PASSWORD}
volumes:
- n8n-redis:/data
n8n:
<<: *shared
image: n8nio/n8n:${VERSION}
command: start
ports:
- ‘5678:5678’
depends_on:
- n8n-postgres
- n8n-redis
n8n-worker:
<<: *shared
image: n8nio/n8n:${VERSION}
command: worker
depends_on:
- n8n
n8n-webhook:
<<: *shared
image: n8nio/n8n:${VERSION}
command: webhook
ports:
- ‘5679:5678’
depends_on:
- n8n

volumes:
n8n-postgres:
driver: local
driver_opts:
type: ‘none’
o: ‘bind’
device: ‘/opt/n8n/postgres’
n8n-redis:
driver: local
driver_opts:
type: ‘none’
o: ‘bind’
device: ‘/opt/n8n/redis’
n8n:
driver: local
driver_opts:
type: ‘none’
o: ‘bind’
device: ‘/opt/n8n/storage’

Hi @genius :wave: I’m not too sure on this - perhaps you have a worker connection that was interrupted, or a worker no longer exists? :thinking:

@krynble might be the best person to try to help you out with diagnosing this :bowing_man:

Hello @genius

Thanks for pinging me @EmeraldHerald

That’s an odd issue, I just tested using the webhook process and it’s all working fine.

The way this works is that the n8n main is the one who should get the execution to run again after the Wait period expires. Can you try setting N8N_LOG_LEVEL=debug?

In your main instance logs you should see an entry similar to the one below, about the Wait tracker. If not, then there’s something wrong with your main n8n.

If everything is all right in main, then it might be a specific issue with Postgres. Can you please then check your database’s execution_entity table and see if the waitTill column contains any data?

1 Like