Cloudflare Workers: Dashboard always queries the original Analytics Engine dataset instead of the configured dataset

[mstander]

Hi,

I'm trying to run two completely separate Sink installations on Cloudflare Workers.

Previously, I had both domains deployed via Cloudflare Pages, and both shared a single Analytics Engine dataset called sink.

I've now migrated both sites to Cloudflare Workers (v0.3.0) and want each installation to have its own Analytics Engine dataset.

Setup

For each Worker I created completely separate resources:

Separate Worker
Separate D1 database
Separate KV namespace
Separate Analytics Engine dataset
Separate R2 bucket

For example:

Domain 1

Analytics Engine dataset: sinkdomain1
DEPLOY_ANALYTICS_DATASET=sinkdomain1
ANALYTICS In Binding is also set to sinkdomain1

Domain 2

Analytics Engine dataset: sinkdomain2
DEPLOY_ANALYTICS_DATASET=sinkdomain2
ANALYTICS In Binding is also set to sinkdomain2

The Worker bindings are correctly configured, and I can confirm that new events are being written into the correct Analytics Engine dataset.

Problem

Although writes go to the correct dataset, the Sink dashboard continues to display analytics from the original sink dataset instead of the newly configured dataset.

In other words:

Worker writes → sinkdomain1 ✅
Cloudflare Analytics Engine shows new events in sinkdomain1 ✅
Sink dashboard still displays data from the old sink dataset ❌

Questions
Is it currently supported to run multiple Sink installations against different Analytics Engine datasets?
Should the dashboard be querying the dataset configured by DEPLOY_ANALYTICS_DATASET, or is there another configuration option required?
Is this expected behaviour, or is this a bug?

I'm happy to provide additional configuration details or help test a fix if needed.

[miantiao-me]

Was NUXT_DATASET missed in the configuration?

[mstander]

I think I found the issue.

When I used an Analytics Engine dataset named sink-domain1, data was written to it successfully, but the Stats dashboard returned errors.

After renaming the dataset to sinkdomain1 (removing the hyphen), everything started working correctly.

Throughout testing, I kept both variables in sync:

NUXT_DATASET (runtime variable)
DEPLOY_ANALYTICS_DATASET (build variable)

So it appears that using a hyphen in the Analytics Engine dataset name causes the Stats backend to fail, even though data is still written successfully.