workers-help
pages-help
general-help
durable-objects
workers-discussions
pages-discussions
wrangler
coding-help
kv
🦀rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
⚡instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd
web3
🤖turnstile
radar
web-research
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows-beta
CF-Worker and MongoDB connection and performance is very slow
Whats the best way to push worker logs into a Graphana Loki instance?
CLW error:
Observability
observability.enabled = true
actually does :/Scheduled Worker failed(?) halfway but no errors shown.
Free Tier Subrequests 50/request??
How to cache worker response?
Get Current Worker file
How can I get my currently deployed worker file.
How can I get my currently deployed worker file.
RPC not working with getters
bar
is not a function. I'm looking to call WORKER.foo.bar()
instead of WORKER.foo().bar()
.
```ts
class Foo extends RpcTarget {
bar() {
return "baz"...The requested Worker version could not be found, please check the ID being passed and try again.
Scheduled worker gets an error in production, not locally
Cache access token requested from an API and use it in the subsequent requests
POST
request (by passing the username and password in the request body). This access token is valid for 1 week (604800 seconds). Is there a way to cache this token that is being returned as part of the response body?
There are two additional API calls (1 POST
+ 1 GET
) within the same worker that uses this access token to get additional data from the API server (that is never cached). At this moment, every time I call worker endpoint, it generates a new token during the 1st call. I'm looking to avoid that and reuse the same token for those additional 2 calls....Wildcard DNS with workers on a custom domain
route = { pattern = "*example.com/*", zone_name = "example.com" }
route = { pattern = "*example.com/*", zone_name = "example.com" }
Using a proxy server with fetch
Old assets availability with `--old-asset-ttl`
--old-asset-ttl
option (Thanks for @Peter Belbin https://github.com/cloudflare/workers-sdk/pull/3384).
Unfortunately, assets aren't available using the old link from the browser after deployment. They are still in KV as expected but are not present in __STATIC_CONTENT_MANIFEST
anymore. So can't be reached from browser by initial name (without hash prefix).
I'm using a custom build with webpack to build my React app (not Wrangler internal bundler)
and npx wrangler deploy -c wrangler.toml -e "<MY_ENV>" --old-asset-ttl=43200
to deploy.
...Switch account deployment targets
Stripe error 500
525 Error when making API Call over worker