You will be billed for the Dispatch Worker invocation, but not for any user Worker invocations
You will be billed for the Dispatch Worker invocation, but not for any user Worker invocations

‘User Workers’ meaning… These would be workers that I am deploying on behalf of the customer… do customers have visibility of these workers/source code from their dashboard? I presume not (I would hope)
D1 and R2 access from these User Workers… this would be to MY instance yes? And I would be responsible for ensuring segregation of data as appropriate?
Placing limits for customers… This would be something I would need to implement myself from the dispatch worker correct?
tag (not tags) field on the script object?

Workers for Platforms Scripts (I have this section in our bill).AAAA 100::, origin seems fine, hostname added, validation completed – but when I access the customer domain (that should be now pointing to my fallback origin (worker)), I always get a cf page with 522. wrangler@dispatch-namespaces-dev release seems to be 4 months oldtagtagsscript export default {
async fetch(req, env) {
const worker = env.DISPATCHER.get("customer-worker-1");
return await worker.fetch(req);
},
};Workers for Platforms ScriptsAAAA 100::wrangler@dispatch-namespaces-dev