Description
Telegram channel die away at next morning after idle for a night or more time.
But It seems nullclaw work well at backend:
[ec2-user@ip-<...> ~]$ nullclaw agent -m "ping"
info(memory): memory plan resolved: backend=hybrid retrieval=keyword vector=none rollout=off hygiene=true snapshot=false cache=false semantic_cache=false summarizer=false sources=1
pong
[ec2-user@ip-<...> ~]$ nullclaw service status
Service state: active
Unit: /home/ec2-user/.config/systemd/user/nullclaw.service
Expected behavior
Telegram channel should respond as usual.
Steps to reproduce
- deploy
nullclaw in AWS Lightsail instance (AWS Linux 2023)
- start
nullclaw service
- configure
telegram channel
- talk with
nullclaw through telegram
- idle for a night or more time
telegram die away whill nullclaw work well at backend
Version
v2026.5.29
OS
Linux
Description
Telegramchannel die away at next morning after idle for a night or more time.But It seems
nullclawwork well at backend:Expected behavior
Telegramchannel should respond as usual.Steps to reproduce
nullclawin AWS Lightsail instance (AWS Linux 2023)nullclawservicetelegramchannelnullclawthroughtelegramtelegramdie away whillnullclawwork well at backendVersion
v2026.5.29
OS
Linux