Does every user worker get 128 MB of memory of their own?

KKai Does every user worker get 128 MB of memory of their own?

H

Every isolate does. If you have multiple requests to the same server, it may start two Worker instances in the same isolate, and thus it will share the 128 MB

HHello, I’m Allie!Every isolate does. If you have multiple requests to the same server, it may sta...

K

KaiOP•6/16/24, 3:02 PM

Oh yeah, makes sense. User workers are just workers. Thanks!

K

KaiOP•6/16/24, 4:12 PM

Just realized when looking through the cf bill that I'm not subscribed to the plan to access wfp (got access before it was released outside of Enterprise), I've submitted a support ticket but currently only on the workers paid plan so i was put at the end of the queue.

Is there somebody I can directly contact to get this resolved?

KKai https://tenor.com/view/oh-me-saturday-night-live-snl-uso-performance-thats-me-ca...

P

Puliczek•6/19/24, 7:57 AM

@Kai @rob Can you share landing page? Really qurious how you describe integration process

PPuliczek @Kai @rob Can you share landing page? Really qurious how you describe integratio...

K

KaiOP•6/19/24, 8:10 AM

Sure https://tryflot.com.

The process of integrating WFP was very smooth in my opinion, the only problem i faced was passing state that's attached to the session without polluting the incoming request. I ended up going with putting that state into the params_object parameter and attaching a outbound worker to grab the state from the user worker.

Flot

Flot - A workflow automation platform

A workflow automation platform that allows you to quickly connect your favorite apps and services together.

KKai Just realized when looking through the cf bill that I'm not subscribed to the pl...

R

rob•6/19/24, 11:57 AM

@tanushree │ Workers PM should be able
To help you tbh ,always very helpful

A

Andreas H•6/20/24, 2:04 PM

Hey, is there a way to get hands on an error code (e.g. https://developers.cloudflare.com/workers/observability/errors/#identify-errors-workers-metrics) when invoking a user worker from a dispatch worker fails? The only "useful" thing that seems to be available on the exception that is being thrown is a name property that probably loosely maps to those code but I'd really prefer something more explicit.

Cloudflare Docs

Errors and exceptions · Cloudflare Workers docs

Review Workers errors and exceptions.

D

DORSHT•6/21/24, 12:31 PM

Hi, question regarding pricing and plans.
If i purchased WFP on my account, do i still need to purchase Workers Paid for anything? Also, how does my domain plan comes into to play here? will the plan (free / pro / business) of the domain i attached to my dispatch worker affect it?

Thanks.

OOle Melhus Can we upload source maps with the wfp user script?

W

Walshy•6/21/24, 1:40 PM

you should be able to yes

DDORSHT Hi, question regarding pricing and plans. If i purchased WFP on my account, do i...

W

Walshy•6/21/24, 1:43 PM

You probably don't need it but I'd recommend having it
as for the zone plan, doesn't play a factor in Workers

E

Erisa•6/22/24, 8:09 AM

If you're on a startup plan then contact support, it likely needs manually enabling

R

Rahul Raikwar•6/25/24, 1:32 PM

"Cloudflare webhook is being called multiple times, and builds are being created repeatedly. Is there any way to stop this?"

RRahul Raikwar "Cloudflare webhook is being called multiple times, and builds are being created...

H

Hard@Work•6/25/24, 1:41 PM

?channel-crossposting

F

Flare•6/25/24, 1:41 PM

Please do not post your question in multiple channels per the rules at #

welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.

R

rob•7/2/24, 7:15 PM

so like: scriptName.org.website.com/* would trigger the dispatch worker ? Im trying to add a route in workers route

R

rob•7/2/24, 8:00 PM

what else do i need to do besides adding the route to the dispatch worker? bc i added

*.domain.com/*

*.domain.com/*

*.domain.com/*

*.domain.com/* i get

DNS_PROBE_FINISHED_NXDOMAIN -- What do i need to set it to on DNS management for the doamin on cloudflare * and point it to 192.0.0.2 . Proxied?

D

DarkDeviL•7/2/24, 8:10 PM

AAAA

AAAA

AAAA

AAAA towards

100::

100::

100::

100::, Proxied ( :cloudflare: ).

R

rob•7/2/24, 8:12 PM

so * 100:: proxied

R

rob•7/2/24, 8:19 PM

hm.. ERR_SSL_VERSION_OR_CIPHER_MISMATCH

R

rob•7/2/24, 9:33 PM

Any ideas, on the cipher mismatch -prob because the CF cert doesnt cover double subdomains right? I need an advanced cert for that or my own external off of cf ?

Rrob Any ideas, on the cipher mismatch -prob because the CF cert doesnt cover double ...

E

Erisa•7/2/24, 9:47 PM

Your answer to your own question is correct - the cipher mismatch error means there's no matching edge certificate on Cloudflare, for second-level subdomains this is because the default Universal SSL does not support them. The fix is to issue an advanced certificate (requires purchasing ACM for $10/mo) or upload your own certificate (requires a Business plan, $250/mo)

Please note if you plan to make use of double level wildcards in your application e.g.

*.*.domain.com

*.*.domain.com

*.*.domain.com

*.*.domain.com, this is not possible for a single SSL/TLS certificate due to inherent TLS protocol restrictions. You will need to issue a new certificate (or hostname for existing certificate) for each first level wildcard e.g.

*.org1.domain.com

*.org1.domain.com

*.org1.domain.com

*.org1.domain.com,

*.org2.domain.com

*.org2.domain.com

*.org2.domain.com

*.org2.domain.com and so on.

R

rob•7/2/24, 9:48 PM

Oh i see! so if i wanred to do scriptName.userName.mydoamin.com thats a no go on double wildcard, i'd have to actually buy a cert for each "userName" correct? -- i couldnt just buy the $10 advanced and cover it

R

rob•7/2/24, 9:49 PM

OR let customers point their domain and then its just a sub domain for their domain for each diff worker/script

R

rob•7/2/24, 9:49 PM

hmph.

E

Erisa•7/2/24, 9:51 PM

You can't issue a certificate with two wildcards so you'd have to explicitly include the username in each certificate. You'd likely run against limits pretty fast doing that

R

rob•7/2/24, 9:51 PM

yea or bring my own external ones and roll my own code there.. more overhead lol

E

Erisa•7/2/24, 9:51 PM

Similar services will do

scriptname-username.example.com

scriptname-username.example.com

scriptname-username.example.com

scriptname-username.example.com to bypass this

R

rob•7/2/24, 9:52 PM

yep seems like the way to go, was gonna be my next route , no pun intended ; )

E

Erisa•7/2/24, 9:53 PM

Yeah that's your most realistic option, the path of double wildcard is imo not worth the added struggle

E

Erisa•7/2/24, 9:53 PM

I mean that is what Cloudflare does for workers but.. they can issue certificates without limits aha

R

rob•7/2/24, 9:53 PM

yah i'll reserve that right for the big orange cloud themselves

R

rob•7/2/24, 9:53 PM

yea the big guy upstairs can handle all that

R

rob•7/2/24, 9:55 PM

welp thanks for the help appreciate it

N

Nick Randall•7/4/24, 2:38 AM

Is it possible to use CRON triggers with workers for platforms?

NNick Randall Is it possible to use CRON triggers with workers for platforms?

J

jman•7/4/24, 2:33 PM

I don’t believe so, directly, since I don’t see the CRON config available on the api docs for WFP

https://developers.cloudflare.com/api/

But one alternative would be to trigger with durable object alarms

Cloudflare API Documentation

Interact with Cloudflare's products and services via the Cloudflare API

W

winnepeach•7/6/24, 5:03 AM

Can I call multiple user workers from a dynamic dispatch worker in a single request? And if so, how would that be billed?

R

rob•7/6/24, 11:44 PM

Simultaneously ?

Rrob Simultaneously ?

L

Lume•7/7/24, 1:55 PM

In the same request to the dispatch worker.

L

Lume•7/7/24, 3:52 PM

export default {
    async fetch(request, env) {
        try {
            
            let workerName1 = "worker1";
            let userWorker1 = env.dispatcher.get(workerName1);
            let result1 =  await userWorker1.fetch(request);

            let workerName2 = "worker2";
            let userWorker2 = env.dispatcher.get(workerName2);
            let result2 =  await userWorker2.fetch(request);
        } catch (e) {
            if (e.message.startsWith('Worker not found')) {
    
                return new Response('', { status: 404 });
            }
            return new Response(e.message, { status: 500 });
        }
    },
};

export default {
    async fetch(request, env) {
        try {
            
            let workerName1 = "worker1";
            let userWorker1 = env.dispatcher.get(workerName1);
            let result1 =  await userWorker1.fetch(request);

            let workerName2 = "worker2";
            let userWorker2 = env.dispatcher.get(workerName2);
            let result2 =  await userWorker2.fetch(request);
        } catch (e) {
            if (e.message.startsWith('Worker not found')) {
    
                return new Response('', { status: 404 });
            }
            return new Response(e.message, { status: 500 });
        }
    },
};

export default {
    async fetch(request, env) {
        try {
            
            let workerName1 = "worker1";
            let userWorker1 = env.dispatcher.get(workerName1);
            let result1 =  await userWorker1.fetch(request);

            let workerName2 = "worker2";
            let userWorker2 = env.dispatcher.get(workerName2);
            let result2 =  await userWorker2.fetch(request);
        } catch (e) {
            if (e.message.startsWith('Worker not found')) {
    
                return new Response('', { status: 404 });
            }
            return new Response(e.message, { status: 500 });
        }
    },
};

export default {
    async fetch(request, env) {
        try {
            
            let workerName1 = "worker1";
            let userWorker1 = env.dispatcher.get(workerName1);
            let result1 =  await userWorker1.fetch(request);

            let workerName2 = "worker2";
            let userWorker2 = env.dispatcher.get(workerName2);
            let result2 =  await userWorker2.fetch(request);
        } catch (e) {
            if (e.message.startsWith('Worker not found')) {
    
                return new Response('', { status: 404 });
            }
            return new Response(e.message, { status: 500 });
        }
    },
};

Can I do something like this, and how is this billed?