What versions & operating system are you using?
System:
OS: Linux 6.17 Ubuntu 24.04.4 LTS 24.04.4 LTS (Noble Numbat)
CPU: (88) x64 Intel(R) Xeon(R) w9-3575X
Memory: 199.98 GB / 250.93 GB
Container: Yes
Shell: 5.2.21 - /bin/bash
Binaries:
Node: 22.13.0 - /home/kenton/.volta/tools/image/node/22.13.0/bin/node
npm: 10.9.2 - /home/kenton/.volta/tools/image/node/22.13.0/bin/npm
pnpm: 10.22.0 - /home/kenton/.volta/bin/pnpm
npmPackages:
wrangler: ^4.71.0 => 4.71.0
Please provide a link to a minimal reproduction
N/A
Describe the Bug
I use wrangler with remote bindings (particularly the Workers AI binding) a lot. I tend to leave it running in the background all day.
After I've been gone for a bit, when I return to my app and try to perform any action that uses the remote binding, I get an error.
To fix this, I have to restart wrangler.
This happens to me 3-5 times a day and it's quite frustrating! Very often it strikes exactly when
Note that my actual credentials only time out once a day. The other 2-4 times that I hit this, simply restarting wrangler fixes it without any need to log into access again.
Wrangler should detect this situation and recreate its remote binding session automatically.
Please provide any relevant error logs
No response
What versions & operating system are you using?
System:
OS: Linux 6.17 Ubuntu 24.04.4 LTS 24.04.4 LTS (Noble Numbat)
CPU: (88) x64 Intel(R) Xeon(R) w9-3575X
Memory: 199.98 GB / 250.93 GB
Container: Yes
Shell: 5.2.21 - /bin/bash
Binaries:
Node: 22.13.0 - /home/kenton/.volta/tools/image/node/22.13.0/bin/node
npm: 10.9.2 - /home/kenton/.volta/tools/image/node/22.13.0/bin/npm
pnpm: 10.22.0 - /home/kenton/.volta/bin/pnpm
npmPackages:
wrangler: ^4.71.0 => 4.71.0
Please provide a link to a minimal reproduction
N/A
Describe the Bug
I use wrangler with remote bindings (particularly the Workers AI binding) a lot. I tend to leave it running in the background all day.
After I've been gone for a bit, when I return to my app and try to perform any action that uses the remote binding, I get an error.
To fix this, I have to restart wrangler.
This happens to me 3-5 times a day and it's quite frustrating! Very often it strikes exactly when
Note that my actual credentials only time out once a day. The other 2-4 times that I hit this, simply restarting wrangler fixes it without any need to log into access again.
Wrangler should detect this situation and recreate its remote binding session automatically.
Please provide any relevant error logs
No response