You can not. From https://developers.cloudflare.com/workers/platform/limits/#simultaneous-open-conne

You can not.
From https://developers.cloudflare.com/workers/platform/limits/#simultaneous-open-connections

Simultaneous Open Connections are measured from the top-level request, meaning any connections open from Workers sharing resources (for example, Workers triggered via Service bindings) will share the simultaneous open connection limit.

Cloudflare Docs

Limits | Cloudflare Workers docs

Cloudflare Workers plan and platform limits.

CCyb3r-Jak3 You can not. From https://developers.cloudflare.com/workers/platform/limits/#sim...

ra•10/1/24, 1:14 AM

I submitted a request to raise my limit, but never heard back. Has anyone had success in lifting this limit?

Rra I submitted a request to raise my limit, but never heard back. Has anyone had su...

Cyb3r-Jak3OP•10/1/24, 1:15 AM

I'd imagine not.

Rra I submitted a request to raise my limit, but never heard back. Has anyone had su...

Isaac McFadyen•10/1/24, 1:21 AM

I believe (not completely sure but highly likely) that the limit is Cloudflare-wide, meaning it's an underlying limit that is built into the Workers runtime and not a limit that can be easily increased per customer.

IImJasonH I'm interested to try out containerized apps on Workers. The [blog post](https:/...

Isaac McFadyen•10/1/24, 3:08 AM

Unless you have an Enterprise contract that specially permits them, containerized apps aren't currently available for Workers.

Isaac McFadyen•10/1/24, 3:09 AM

The blog post was more a "here's this internal thing we're testing out now that might eventually come to external customers" and less "you can deploy containers to Workers right now"

BC17•10/1/24, 9:55 AM

Feel I've searched and there's different responses and levels of understanding on cache reserve and tiered caching, especially when workers are considered so I just want to clarify

If I am serving a SSR site with workers and static assets, would the following occur;

I cache HTML via origin headers (Astro.header.set) on a short TTL, 15 minutes for example. Would tiered caching ever be utilised here if it was switched on?
If I switch on cache reserve, would the static assets served from the public and _astro directories ever be served from it?

The cache reserve is so we can persist assets across deployments due to stale HTML referencing old assets - maybe this is less so an issue, but feel we seem to get stung by all hosts in this department so having some sort of persistent storage between deployments is useful

Ohad•10/1/24, 9:57 AM

How can I acess KV from Cron worker? ScheduleContextScheduleContext seem to be missing kv field

Ohad•10/1/24, 9:58 AM

oh nvm, via Env

felixv•10/1/24, 12:00 PM

Is there some timeline on when Workflows might launch? Is it more weeks or months away? I was hoping this would be launched during launch week but sadly no

arch•10/1/24, 2:10 PM

Anyone using Zig to run Workers with WASM?

Murder Chicken•10/1/24, 3:31 PM

Is it possible to add some kind of context variable when making RPC calls so that I can consume that from within the WorkerEntrypointWorkerEntrypoint methods? I'm trying to avoid having to pass context variable into every method in the WorkerEntrypointWorkerEntrypoint.

Ggotfredsen I think I read the Cloudflare blog post about container support 10 times until I...

Hello, I’m Allie!•10/1/24, 4:20 PM

This one? https://forms.gle/msrkBLBYNFFYRaqY8

Google Docs

Cloudflare Container Platform — Early Access

w3bcode•10/1/24, 4:31 PM

can someone suggest me a good library for loggers like pino but which will work on cloudflare workers/pages

joshka•10/1/24, 4:46 PM

Is it possible to add a tower_http::trace::TraceLayertower_http::trace::TraceLayer to a worker somehow? In normal non-wasm axum I'd just add .layer(ServiceBuilder::new().trace_for_http()).layer(ServiceBuilder::new().trace_for_http()), but when running with cloudflare I get the unhelpful (seemingly impossible to debug) error:

✘ [ERROR] A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished.

✘ [ERROR] A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished.

joshka•10/1/24, 4:47 PM

(I say impossible because the stacktrace points at a minimized file)

Cconnor Hey! Our company has been migrating our currently Pages/Workers mono repo to run...

texan•10/1/24, 7:00 PM

Hey Conner, thanks for the feedback! I do know that preview URLs should be available for each version of your worker, though I'm not sure about DOs like you mentioned. Happy to pass this feedback along.

FFlikTeoh Question: Will the secrets store ever be available in the near future? https://b...

tadhglewis•10/1/24, 10:58 PM

IIRC it was deprioritised to focus Code Orange initiative

tadhglewis•10/2/24, 1:52 AM

They deprioritised it to work on more important things - platform reliability

FFlikTeoh Haha that was in March though. Do you think the feature will ever made it outsid...

Isaac McFadyen•10/2/24, 2:01 AM

KV is absolutely safe enough if that's what you're worried about.

Isaac McFadyen•10/2/24, 2:02 AM

The only danger with KV is that anyone with full access to your CF account can view KV contents (i.e. if your login is leaked)

FFlikTeoh Haha that was in March though. Do you think the feature will ever made it outsid...

tadhglewis•10/2/24, 2:16 AM

If you're just sharing across workers, I'd upload the secret for each worker during CI - e.g. store the secret in GitHub secrets and upload during CI

That way it's centrally managed

tadhglewis•10/2/24, 2:18 AM

      - name: Deploy worker
        uses: cloudflare/wrangler-action@v3
        with:
          secrets: |
            WORKER_SECRET
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          wranglerVersion: "3.78.4"
        env:
          WORKER_SECRET: ${{ secrets.WORKER_SECRET_FROM_GITHUB_SECRETS }}

      - name: Deploy worker
        uses: cloudflare/wrangler-action@v3
        with:
          secrets: |
            WORKER_SECRET
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          wranglerVersion: "3.78.4"
        env:
          WORKER_SECRET: ${{ secrets.WORKER_SECRET_FROM_GITHUB_SECRETS }}

tadhglewis•10/2/24, 2:22 AM

Cloudflare Secrets Store main use case is for everything else, not for sharing secrets across workers - for example, you might have internal developer tooling/scripts which pull from Secrets Store or Terraform or applications in AWS etc

E: I guess in the future you could also pull from Secrets Store during CI instead of GitHub Secrets* but GitHub Actions already has access to sensitive data (inc cloudflare api token) so I think doing ^ is fine

tadhglewis•10/2/24, 2:26 AM

Ah yep Workers Builds definitely changes things... That's my biggest gripe with it... Are you supposed to clickops Worker secrets if you use Workers Builds?

GitHub already has access to sensitive data so I think it's better to centralise secrets there

FFlikTeoh And they forgot about the feature?

Walshy•10/2/24, 2:40 AM

Definitely not forgotten about

SameerOP•10/2/24, 5:09 AM

What timezone do cron event uses? UTC?

SameerOP•10/2/24, 5:13 AM

oh yeah it does use UTC

LordSilver•10/2/24, 5:37 AM

Why you need to install Cloudflare Workers app in your GitHub account? Why it cannot simply be an authorized app like all other PaaS/cloud providers?

Elliot Hesp•10/2/24, 12:51 PM

Hi all,

I have a worker and custom hostnames.

I have a fallback hostname with a CNAME to myworkername.<zone>.workers.dev
I have a target hostname with a CNAME to my fallback DNS
I have added the custom hostnames and the fallback to SSL -> Custom Hostnames

I have a workers route on fallback.domain.com/* to point to my worker

Going to fallback.domain.com hits the worker as expected, but my custom hostnames are hitting a 522 error - I am totally stumped as to why

EElliot Hesp Hi all, I have a worker and custom hostnames. I have a fallback hostname wit...

Chaika•10/2/24, 1:04 PM

When your setup is like:

subdomain.customerdomain.com -> fallback.domain.com, Worker Routes sees the incoming request as "subdomain.custerdomain.com/" and thus fallback.domain.com/* wouldn't match. You need a wildcard as per this guide: https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin/ just be careful to exclude your own subdomains first or use a dedicated domain/zone for cf for saas

Cloudflare Docs

Workers as your fallback origin | Cloudflare for Platforms docs

Learn how to use a Worker as the fallback origin for your SaaS zone.

NoireFatale•10/2/24, 6:50 PM

I am trying to troubleshoot an issue with my webpage and I am tryong to check the server logs but they logs won't display?

NoireFatale•10/2/24, 6:51 PM

just says "waiting for logs..." but never populates

NNoireFatale just says "waiting for logs..." but never populates

Ashley•10/2/24, 8:58 PM

Are you using the new persistent logs (you'll have an [observability] section in your wrangler.toml if you do) or real-time logs?

You can not. From https://developers.cloudflare.com/workers/platform/limits/#simultaneous-open-conne

Similar Threads