The closest I figured was `rules = [{ type = "Text", globs = ["**/*.json"], fallthrough = true }]`,

The closest I figured was

rules = [{ type = "Text", globs = ["**/*.json"], fallthrough = true }]

rules = [{ type = "Text", globs = ["**/*.json"], fallthrough = true }]

, but that doesn't seem to be it

manugarderes_•6/12/24, 4:56 PM

hey, I am getting an "Could not start Cloudflare tunnel: max retries reached." error
Do you know if cloudflare is down or something??

MMozzy The closest I figured was `rules = [{ type = "Text", globs = ["**/*.json"], fall...

MozzyOP•6/12/24, 5:06 PM

using

--no-bundle

--no-bundle

MozzyOP•6/12/24, 5:07 PM

It's definitely going to complain about exceeding 10MB, but let's ignore that for now

MozzyOP•6/12/24, 5:34 PM

This works, but is obviously not ideal and very ugly

.gwapes•6/12/24, 6:11 PM

Could just append the platform at the end of the ./data/openbeta/+platform+.json type thing

Original message was deleted

MozzyOP•6/12/24, 6:24 PM

I ended up with the following

MozzyOP•6/12/24, 6:25 PM

Total Upload: 8495.43 KiB / gzip: 1928.18 KiB

MozzyOP•6/12/24, 6:25 PM

Just slightly fat, but it's fine

Original message was deleted

MozzyOP•6/12/24, 6:32 PM

That would be very nice

Till | gotoHuman•6/12/24, 6:50 PM

Hey there, question regarding email workers: Is it possible to use plus addressing with it?

TTill | gotoHuman Hey there, question regarding email workers: Is it possible to use plus addressi...

Chaika•6/12/24, 6:51 PM

wildcard email worker and implement it yourself? sure

Till | gotoHuman•6/12/24, 6:58 PM

I'm talking about the route of the worker ("Binding the Email Worker to a route. This is the email address that forwards emails to the Worker."), so if it is assignedWorkerEmail@sub.cloudflare.com, can I also use assignedWorkerEmail+abcdef@sub.cloudflare.com

Till | gotoHuman•6/12/24, 6:58 PM

Not sure what you mean by "wildcard email worker" and which part I should implement myself

TTill | gotoHuman I'm talking about the route of the worker ("Binding the Email Worker to a route....

Chaika•6/12/24, 7:02 PM

can I also use assignedWorkerEmail+abcdef@sub.cloudflare.com

Chaika•6/12/24, 7:03 PM

https://developers.cloudflare.com/email-routing/postmaster/#signs-such--and--are-treated-as-normal-characters-for-custom-addresses

Chaika•6/12/24, 7:03 PM

Signs such “+” and “.” are treated as normal characters for custom addresses

Email Routing does not have advanced routing options. Characters such as + or ., which perform special actions in email providers like Gmail and Outlook, are currently treated as normal characters on custom addresses. More flexible routing options are in our roadmap.

Chaika•6/12/24, 7:04 PM

I was saying you can assign a worker to the wildcard route and implement plus routing yourself, but yea not built in

f8•6/12/24, 7:36 PM

Is there way to rerun cron job if it fails overriding the scheduled trigger.

Ff8 Is there way to rerun cron job if it fails overriding the scheduled trigger.

Chaika•6/12/24, 7:46 PM

you can manually call the scheduled handler from a fetch event, ex:

   if (newurl.pathname === "/supersecretfetchmetotriggercron" && request.headers.has("APIKEY") && request.headers.get("APIKEY") === env.CRONAPIKEY) {
// if you're using any properties of the event like cron/etc you can recreate it instead of passing null
      await this.scheduled(null, env, ctx);
      return new Response("ok - triggered");
    }

   if (newurl.pathname === "/supersecretfetchmetotriggercron" && request.headers.has("APIKEY") && request.headers.get("APIKEY") === env.CRONAPIKEY) {
// if you're using any properties of the event like cron/etc you can recreate it instead of passing null
      await this.scheduled(null, env, ctx);
      return new Response("ok - triggered");
    }

CChaika you can manually call the scheduled handler from a fetch event, ex: ```js if ...

f8•6/12/24, 7:47 PM

Gotcha, how would i know it fails to then call this

Ff8 Gotcha, how would i know it fails to then call this

Chaika•6/12/24, 7:47 PM

oh you mean automatically retry on failure?

CChaika oh you mean automatically retry on failure?

f8•6/12/24, 7:47 PM

yes

f8•6/12/24, 7:48 PM

my cron runs every hour. if it fail i want it to run right after again

Chaika•6/12/24, 7:48 PM

nothing native, I mean you could just extract your cron logic to a different function and try.. cronfunc() catch.. cronfunc() but a bit silly lol, it usually makes more sense to specifically retry what could fail/scope your retries better

Chaika•6/12/24, 7:48 PM

does your cron rely on a third party api fetch that can fail? Just have that part retry, etc

Chaika•6/12/24, 7:50 PM

of course there are specific conditions for the retry being able to work like that. If you run out of resources (cpu, mem), it's just going to fail

johtso•6/12/24, 9:51 PM

is there anything that will show what your workers usage is as a proportion of your plan's included usage?

johtso•6/12/24, 9:51 PM

those two things seem rather disjointed at the moment

johtso•6/12/24, 9:52 PM

even a 3rd party tool

johtso•6/12/24, 9:52 PM

I know I'm way bellow the allowance, but it still freaks me out not being able to see it

samuelarogbonlo•6/12/24, 10:09 PM

Hello Folks,

I'm having an issue with my Cloudflare workers and need some help. I have two workers in different Cloudflare accounts:

Worker 1 in Account 1 with the domain `example.com` and routes:
- test.example.com/list/fruits
- test.example.com/list/animals
  - Worker 2 in Account 2 with the domain `myexample.com` and routes:
  - test.myexample.com/list/fruits
  - test.myexample.com/list/animals
    I want to update Worker 2 to use the routes from Worker 1. How can I configure cross-account worker domain access to achieve this?

johtso•6/12/24, 10:58 PM

maybe you could proxy requests to the other domain using a worker?

f8•6/13/24, 12:28 AM

when i run my cronjob locally via curl "http://localhost:56968/__scheduled?cron=0+*+*+*+*" it begins running what's in my async scheduled { } body. After about a minute it reruns eventhough im setting cron to 0 * * * *

f8•6/13/24, 12:28 AM

Why is this the case?

f8•6/13/24, 4:04 AM

Are cron's cpu limit 15min or 30s for standard plan when set to run exactly once every hour? Running locally mine I get a cpu time limit after 50000ms but wondering if this is just because it's not given 15min locally because it can be ran more than every hour?

f8•6/13/24, 4:23 AM

"On the Unbound billing model, 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."

Isn't unbound model deprecated and now is standard model? Does this 15 minutes still apply? Also what happens if it runs exactly every hour. Technically says "more than 1 hour" but what if it's every one hour

nehatkhan•6/13/24, 4:23 AM

I have created a Hono js app with node js adapter, how to deploy the app to cloudfare workers. Please help

Nnehatkhan I have created a Hono js app with node js adapter, how to deploy the app to clou...

Sam•6/13/24, 8:39 AM

https://developers.cloudflare.com/workers/wrangler/commands/#deploy

Cloudflare Docs

Commands - Wrangler · Cloudflare Workers docs

Create, develop, and deploy your Cloudflare Workers with Wrangler commands.

cosbgn•6/13/24, 10:47 AM

What's canceled?

Erisa•6/13/24, 11:03 AM

The user/client making the request cancelled the request before it could complete

Erisa•6/13/24, 11:04 AM

you would get this if you for example ran

curl

curl

against a url and then did ctrl+c to cancel it before it finished, or loaded a webpage and then closed the tab or pressed the X to stop loading before it finished

cosbgn•6/13/24, 11:05 AM

Ok thanks

cosbgn•6/13/24, 11:18 AM

@Erisa I'm sending a cron, and cf is returning a 524 and "canceled" - Is this a timeout from workers or from my cron provider?

cosbgn•6/13/24, 11:18 AM

the cron job is not from cf, it's another platform

cosbgn•6/13/24, 11:19 AM

Seems to die at 100 seconds exact

cosbgn•6/13/24, 11:27 AM

even if the cron calls directly /api ? does it still pass through the cdn?

cosbgn•6/13/24, 11:28 AM

so workers practically can't run longer than 100 seconds unless send back a stream

cosbgn•6/13/24, 11:28 AM

or maybe if I move the logic inside waitUntill it could run without the 100 second limit?

cosbgn•6/13/24, 11:29 AM

or maybe instead of relying on http crons I could use cloudflare ones, that should avoid the 100 second response issue

cosbgn•6/13/24, 11:30 AM

So the best solution is using cloudflare cron triggers, right?

if (newurl.pathname === "/supersecretfetchmetotriggercron" && request.headers.has("APIKEY") && request.headers.get("APIKEY") === env.CRONAPIKEY) { // if you're using any properties of the event like cron/etc you can recreate it instead of passing null await this.scheduled(null, env, ctx); return new Response("ok - triggered"); }

The closest I figured was `rules = [{ type = "Text", globs = ["**/*.json"], fallthrough = true }]`,

Similar Threads

Similar Threads

Similar Threads