Deploying with wrangler.toml with a Service Binding stuck in Queued state
I have a Next.js app I'm trying to deploy to Pages, that has a Service Binding. The only problem is that when I run 
The only reason I didn't tag
wrangler deploy [...] it all shows successfully in my CLI, but in the Pages Deployments list page, the new deployment shows up in the "Queued" state forever. There are no errors as far as I can tell, and the UI doesn't really show any useful information. If I deploy without the Service Binding - that deployment goes through fine. Then if I go to the settings and manually add the Service Binding (which also requires me to have done the deploy without the wrangler.tomlnext-on-pages is because I also deployed a Remix app last week and, from memory, it did the exact same thing. At the time I just assumed it was a problem with Remix, hence switching to Next.js. But it just appears to be a wrangler.toml issue, maybe?