with custom "cache key" in worker ? is free ? - Cloudflare Developers

© 2026 Hedgehog Software, LLC

More

Communities Docs About Terms Privacy

samsung

Ssamsung with custom "cache key" in worker ? is free ?

Hello, I’m Allie!

H

Hello, I’m Allie!•12/14/24, 6:30 AM

Yes, that’s free

Aster

A

Aster•12/14/24, 6:36 AM

Hello

do you know if it is possible, using a cloudflare tunnel, to send HTTP requests from a web server running on a VPS to a cloudflare worker without exposing the worker endpoint publicly?

so:

Worker private endpoint <-> tunnel <-> web server somewhere (k8s, vps)

samsung

S

samsungOP•12/14/24, 6:42 AM

Requests to static assets are free and unlimited. https://developers.cloudflare.com/workers/platform/pricing/ but this is not static assest.

Cloudflare Docs

Pricing · Cloudflare Workers docs

Workers plans and pricing information.

samsung

S

samsungOP•12/14/24, 6:45 AM

fetch(event.request, { cf: { cacheKey: "some-string" } }); with cacheTtl

Ashley

A

Ashley•12/14/24, 1:31 PM

Has anyone had any success passing large files from a Worker to an RPC Entrypoint? I tried passing the File itself and it errors (AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value: from the client - doesn't even hit the RPC endpoint)

Then I tried passing the arrayBuffer - this works, but there are limits on RPC method calls of 1MiB so that naturally isn't going to work. I tried passing a ReadableStream (file.stream()) and it is passed, and is close, but then I get

Uncaught (in promise) TypeError: Provided readable stream must have a known length (request/response body or readable half of FixedLengthStream)

Uncaught (in promise) TypeError: Provided readable stream must have a known length (request/response body or readable half of FixedLengthStream)

And while it is a ReadableStream, it has no length for whatever reason (it seems to go from being a non-BYOB to a BYOB and length is undefined). Probably some JS-specifics I'm missing, anyone got any ideas?

johtso

J

johtso•12/14/24, 4:23 PM

I've suddenly started getting The uploaded script has no registered event handlers. [code: 10068]The uploaded script has no registered event handlers. [code: 10068], I don't think I've changed anything that would cause this.. any ideas how I could figure out what's going on?

johtso

J

johtso•12/14/24, 4:28 PM

my worker export defaultexport defaults an object with a fetch handler, I don't see why this error would start appearing

johtso

J

johtso•12/14/24, 4:29 PM

I do also see A request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failedA request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failed

johtso

J

johtso•12/14/24, 5:10 PM

when running wrangler dev i get "service core:user:email-sender: Uncaught Error: Top-level await in module is unsettled.", but that makes no sense to me either

johtso

J

johtso•12/14/24, 5:14 PM

some kind of circular dependency?

D Trombett

D

D Trombett•12/14/24, 5:22 PM

Not sure if it's a bug or what but do you have a top-level await? What are your imports?

johtso

J

johtso•12/14/24, 5:27 PM

No, I shouldn't have a top level await, I have quite a few imports..

import { queries } from 'database'
import { handleWebhookRequest } from './postmark-webhook.js';
import { ConfigProvider, Effect, Either, Layer, pipe } from 'effect';
import { AppConfig, AppConfigSchema, MainDatabase, MembershipsDatabase, Lock, TracingAll, tryQuery } from './services.js';
import { handleEmailJobs } from './email-sending.js';
import * as Postmark from './postmark/postmark';
import { FetchHttpClient } from '@effect/platform';
import { Schema as S } from 'effect';
import * as Tracer from "@effect/opentelemetry/Tracer"
import { trace } from "@opentelemetry/api";
import { EmailJobBodySchema, MembershipRenewalEmailJobBodySchema } from './schemas.js';
import { honkAll } from './slack-honks.js';

import { queries } from 'database'
import { handleWebhookRequest } from './postmark-webhook.js';
import { ConfigProvider, Effect, Either, Layer, pipe } from 'effect';
import { AppConfig, AppConfigSchema, MainDatabase, MembershipsDatabase, Lock, TracingAll, tryQuery } from './services.js';
import { handleEmailJobs } from './email-sending.js';
import * as Postmark from './postmark/postmark';
import { FetchHttpClient } from '@effect/platform';
import { Schema as S } from 'effect';
import * as Tracer from "@effect/opentelemetry/Tracer"
import { trace } from "@opentelemetry/api";
import { EmailJobBodySchema, MembershipRenewalEmailJobBodySchema } from './schemas.js';
import { honkAll } from './slack-honks.js';

johtso

J

johtso•12/14/24, 5:27 PM

I guess I'll start stripping things away one by one..

D Trombett

D

D Trombett•12/14/24, 6:32 PM

I honestly have no idea how would you debug such error because I've had it too in the past and it is a pain but are you sure you don't have other logs before it?

D Trombett

DD Trombett I honestly have no idea how would you debug such error because I've had it too i...

johtso

J

johtso•12/14/24, 6:35 PM

all I get is

⎔ Starting local server...
✘ [ERROR] service core:user:email-sender: Uncaught Error: Top-level await in module is unsettled.

⎔ Starting local server...
✘ [ERROR] service core:user:email-sender: Uncaught Error: Top-level await in module is unsettled.

when running workers devworkers dev

johtso

J

johtso•12/14/24, 6:36 PM

when trying to deploy I get

✘ [ERROR] A request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failed.

  The uploaded script has no registered event handlers. [code: 10068]

✘ [ERROR] A request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failed.

  The uploaded script has no registered event handlers. [code: 10068]

johtso

Jjohtso when trying to deploy I get ``` ✘ [ERROR] A request to the Cloudflare API (/acco...

D Trombett

D

D Trombett•12/14/24, 6:46 PM

Uh, wait, does Cloudflare use commonjs in production? It's strange that you don't get the same error

johtso

J

johtso•12/14/24, 7:26 PM

ok, finally found the culprit after a whole day of commenting out code

johtso

J

johtso•12/14/24, 7:26 PM

and yes, it was a top level await that I'd added while testing things

johtso

J

johtso•12/14/24, 7:26 PM

I wonder if there's a more efficient way to find the offending code in a situation like this?

johtso

Jjohtso I wonder if there's a more efficient way to find the offending code in a situati...

Hello, I’m Allie!

H

Hello, I’m Allie!•12/14/24, 7:36 PM

A linter rule maybe?

johtso

J

johtso•12/14/24, 7:36 PM

yeah, I definitely need to set up some linting and typescript error checking for this project

johtso

J

johtso•12/14/24, 7:37 PM

also a lesson to commit early and often, the smaller the diff between your last working version and your current code, the less places there are for a new issue to hide and the fewer potential red herrings

johtso

J

johtso•12/14/24, 7:38 PM

don't do a big dependency update and write some new code without committing in between

MrBithles

M

MrBithles•12/15/24, 8:02 AM

For a local worker with remote flag that is setup with RPC (WorkerEntrypoint) and using browser render with queues is it possible to call worker's fetch locally because I only get 500 response and no logs to why. (Need to have remote flag because browser render doesn't work on local wrangler)

Worker code snippet

export default class Entrypoint extends WorkerEntrypoint {
  async fetch(req: Request) {
    console.log('fetch'); // this is not logged
    return new Response('ok');
  }

  async queue(batch: MessageBatch<Message>) {
    // this runs on deployed workers fine
  }
}

export default class Entrypoint extends WorkerEntrypoint {
  async fetch(req: Request) {
    console.log('fetch'); // this is not logged
    return new Response('ok');
  }

  async queue(batch: MessageBatch<Message>) {
    // this runs on deployed workers fine
  }
}

Calling worker via localhost

curl -X POST http://localhost:8787

curl -X POST http://localhost:8787

Logs from wrangler dev, but I don't see my console log in fetch

[wrangler:inf] POST / 500 Internal Server Error

[wrangler:inf] POST / 500 Internal Server Error

Shayan

SShayan I have a CRON worker (Worker A) that fetches my database and gets a list of ID's...

Hello, I’m Allie!

H

Hello, I’m Allie!•12/15/24, 7:35 PM

You can use a Service Binding instead of fetching.

Cloudflare Docs

Service bindings - Runtime APIs · Cloudflare Workers docs

Facilitate Worker-to-Worker communication.

Walshy

W

Walshy•12/15/24, 10:32 PM

https://en.m.wikipedia.org/wiki/CPU_time
tldr is that its compute time. If you're waiting for a fetch call for example, that is not counted.

Walshy

W

Walshy•12/16/24, 12:43 AM

Yes

Walshy

W

Walshy•12/16/24, 3:18 AM

i assume you're on free plan

Walshy

W

Walshy•12/16/24, 3:20 AM

if so, yeah the limit is 10ms so it will cut you off. we don't have a hard cut off at 10ms though, we allow you to go higher (to account for spikes, variance or what have you). if you consistently are higher then you'll see your cpu time exceeded

Walshy

W

Walshy•12/16/24, 3:20 AM

yes

Walshy

W

Walshy•12/16/24, 3:25 AM

https://developers.cloudflare.com/workers/platform/limits/#worker-limits
https://developers.cloudflare.com/workers/platform/limits/#cpu-time

Walshy

W

Walshy•12/16/24, 3:26 AM

Scheduled Workers (Cron Triggers) have different limits on CPU time based on the schedule interval. When the schedule interval is less than 1 hour, a Scheduled Worker may run for up to 30 seconds. When the schedule interval is more than 1 hour, a scheduled Worker may run for up to 15 minutes.

rdutton

R

rdutton•12/16/24, 3:33 AM

Looking at Shayan's code for Worker A, are the fetches to Worker B guaranteed to occur given there is no 'await' before the worker returns it's response?

Lulu

L

Lulu•12/16/24, 5:43 AM

I looked at the compatibility matrix for workers / pages, and the features I need are supported in both. At this point would there be any advantage in using one over the other? I know the Frameworks feature is still in beta for Workers but that doesn't matter to me atm.

Lulu

LLulu I looked at the compatibility matrix for workers / pages, and the features I nee...

Hello, I’m Allie!

H

Hello, I’m Allie!•12/16/24, 5:46 AM

From a roadmap perspective, Workers are the future. While they don’t quite have all of the features you might need for website hosting like Pages do, they are the first to get new features when they launch, and some new features may only launch on Workers

rdutton

R

rdutton•12/16/24, 6:00 AM

For me the missing pieces from Pages are logging and queue consumption. Now that Workers have static assets and noting the above comment, I might try to migrate some projects from Pages to Workers.

sathoro

S

sathoro•12/16/24, 6:40 AM

we use both. frontend on Pages, backend on Workers. it is actually nice to be able to deploy them separately

import { queries } from 'database'
import { handleWebhookRequest } from './postmark-webhook.js';
import { ConfigProvider, Effect, Either, Layer, pipe } from 'effect';
import { AppConfig, AppConfigSchema, MainDatabase, MembershipsDatabase, Lock, TracingAll, tryQuery } from './services.js';
import { handleEmailJobs } from './email-sending.js';
import * as Postmark from './postmark/postmark';
import { FetchHttpClient } from '@effect/platform';
import { Schema as S } from 'effect';
import * as Tracer from "@effect/opentelemetry/Tracer"
import { trace } from "@opentelemetry/api";
import { EmailJobBodySchema, MembershipRenewalEmailJobBodySchema } from './schemas.js';
import { honkAll } from './slack-honks.js';

import { queries } from 'database'
import { handleWebhookRequest } from './postmark-webhook.js';
import { ConfigProvider, Effect, Either, Layer, pipe } from 'effect';
import { AppConfig, AppConfigSchema, MainDatabase, MembershipsDatabase, Lock, TracingAll, tryQuery } from './services.js';
import { handleEmailJobs } from './email-sending.js';
import * as Postmark from './postmark/postmark';
import { FetchHttpClient } from '@effect/platform';
import { Schema as S } from 'effect';
import * as Tracer from "@effect/opentelemetry/Tracer"
import { trace } from "@opentelemetry/api";
import { EmailJobBodySchema, MembershipRenewalEmailJobBodySchema } from './schemas.js';
import { honkAll } from './slack-honks.js';

export default class Entrypoint extends WorkerEntrypoint {
  async fetch(req: Request) {
    console.log('fetch'); // this is not logged
    return new Response('ok');
  }

  async queue(batch: MessageBatch<Message>) {
    // this runs on deployed workers fine
  }
}

export default class Entrypoint extends WorkerEntrypoint {
  async fetch(req: Request) {
    console.log('fetch'); // this is not logged
    return new Response('ok');
  }

  async queue(batch: MessageBatch<Message>) {
    // this runs on deployed workers fine
  }
}