Tail Workers are best for persistent connections, where you are writing your logs to some third syst
Tail Workers are best for persistent connections, where you are writing your logs to some third system
Service Bindings: Can user workers have service bindings configured when they're uploaded to a dispatch namespace? The docs mention that service bindings "don't work in the Workers for Platforms model because User Workers are uploaded ad hoc" but it's not entirely clear if this means user workers can't have ANY service bindings or is this forbidding the use of Service Bindings as a replacement for the WfP dispatch mechanism itself?
Workflows: Are Workflow bindings available in user workers? I couldn't find specific documentation about this.
request.cf: If the cf object always unavailable in WfP?

Tailing is not enabled for your account. Please see our docs for more information: https://developers.cloudflare.com/workers/observability/logs/tail-workers/ I get this when I try and add a tail consumer to a worker in a dispatch namespace though and I dont really see a way to really enable them, should I just add it to the dispatch worker instead in that case?https://api.cloudflare.com/client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/workers/dispatch/namespaces/${DISPATCH_NAMESPACE}/scripts/${WORKER_NAME}/content; This API created a worker and encountered a problem {outbound.parameters property is setrequest.cf? It should be present if you pass it inTailing is not enabled for your account. Please see our docs for more information: https://developers.cloudflare.com/workers/observability/logs/tail-workers/https://api.cloudflare.com/client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/workers/dispatch/namespaces/${DISPATCH_NAMESPACE}/scripts/${WORKER_NAME}/contentoutbound.parametersrequest.cflet userWorker = env.dispatcher.get(workerName);
return await userWorker.fetch(request);