Pages build fail, here's the logs 🤔
Pages build fail, here's the logs 
CTry rerunning. That error message seems to indicate that the node binaries couldn't be downloaded
C3 times, not working
CYeah I am seeing it on build image v2 where it hangs.
Dsame here, works on v1, hangs on v2
Dcc @johndotawesome
CIf deployment ID are needed I have
DIf I want to run a script in all regions every few minutes, would a CF health check be the easiest “hack”?
Jyeah, healthchecks would probably be the easiest way to do that
K[[env.whatever.queues.producers]]
KJust like that
KThe normal queues.producers block is top level (no environment)
Kthen do the env.staging.etc block
IIs there a way to get the last x logs instead of opening a tail?
CNo, Cloudflare isn't storing the logs for you anywhere, Tail works because it's streaming the logs directly to you.
If you want to store the logs yourself, Workers Paid has Workers Trace Events via Logpush, and you can store them in some platform, either using one of the offical integrations or the API-only HTTP destination. You can also use some integration inside your Worker itself to store logs, Honeycomb I think has one, not sure of any good others
If you want to store the logs yourself, Workers Paid has Workers Trace Events via Logpush, and you can store them in some platform, either using one of the offical integrations or the API-only HTTP destination. You can also use some integration inside your Worker itself to store logs, Honeycomb I think has one, not sure of any good others
CNow as well you could use Tail Workers (https://developers.cloudflare.com/workers/platform/tail-workers/), and send the logs wherever you want, Workers Paid required though
IThanks a lot
IIn that case, the API docs appear to have a small issue. https://developers.cloudflare.com/api/operations/worker-tail-logs-list-tails shows returning only a single object, however, it returns an array.
Interact with Cloudflare's products and services via the Cloudflare API
Kwhere can I find documentation about the option in fetch/Response/Request?
edit: I found it for fetch
edit: I found it for fetch
CFun API things, on the bottom left of that page you can click "Give feedback" and submit the issue
COn Request it's RequestInitCfProperties created requests and IncomingRequestCfProperties for requests your worker receives, types documented here: https://developers.cloudflare.com/workers/runtime-apis/request/#incomingrequestcfproperties
The Request interface represents an HTTP request and is part of the Fetch API.
DHi I'm new to CF Workers API,
in my attempt to use the api to create a new worker (https://developers.cloudflare.com/api/operations/worker-script-upload-worker-module) I made it work but the Routes section under it is not activated by default (but this is automatically activated when I use the dashboard)
Can you guys guide me more on this to get it active automatically when calling the API?
in my attempt to use the api to create a new worker (https://developers.cloudflare.com/api/operations/worker-script-upload-worker-module) I made it work but the Routes section under it is not activated by default (but this is automatically activated when I use the dashboard)
Can you guys guide me more on this to get it active automatically when calling the API?
Interact with Cloudflare's products and services via the Cloudflare API
Aanyone else getting errors? I am not able to deploy a new worker. Getting 10002
WHey, we're aware and working on it 
Sorry for the issues, you can stay up to date in #cloudflare-status
Sorry for the issues, you can stay up to date in #cloudflare-status
AAwesome as always!
MSeems like you can't make workers currently?
M
MThat's all I'm getting as soon as I click "Create" button
MMaybe that's lil bit more useful screenshot
W
Wi can't repro
W
WWorker got made for me without an issue
MAlso happens when you click on "Manage application"
W
MCreate one fixed itself after refresh
Walso fine
MHmm
MStill broken for me 
MLemme try to create another one