Failed to fetch widget data

[arifje]

Describe the bug

Calling unknown method: verbb\metrix\sources\Cloudflare::fetchRealtimeData()
/var/www/xxx/cms/vendor/yiisoft/yii2/base/Component.php:312
/var/www/xxx/cms/vendor/verbb/metrix/src/widgets/Realtime.php:49
/var/www/xxx/cms/vendor/verbb/metrix/src/base/WidgetData.php:38
/var/www/xxx/cms/vendor/yiisoft/yii2/caching/Cache.php:608
/var/www/xxx/cms/vendor/verbb/metrix/src/base/WidgetData.php:37

Craft Pro 4.16.4
Sources installed/connected: Cloudflare & Google Analytics

Steps to reproduce

x

Craft CMS version

Craft Pro 4.16.4

Plugin version

1.0.2

Multi-site?

no

Additional context

No response

[engram-design]

These have probably been created from the default widgets, correct? If so, it's assumed you're running Google Analytics for the default widgets we provide - but of course, that's not everyone's default source. For example, some sources like Cloudflare don't support a real-time widget.

So this error is a user-unfriendly way of saying it's not supported by Cloudflare, and you'll want to delete the widget or change it's metric.

[diegocosta-dev]

Hi @engram-design

We experiencing the same issue while using Fathom.
To better illustrate the problem, We recorded a short video with explanations and uploaded it to YouTube:

Watch the video

A server error occurred.
Ge@https://xxx.com/cpresources/1e4a6e73/axios.js?v=1756215744:2:31106
v@https://xxx.com/cpresources/1e4a6e73/axios.js?v=1756215744:2:36222

p@https://xxx.com/cpresources/1e4a6e73/axios.js?v=1756215744:2:3448
u/T/<@https://xxx.com/cpresources/1e4a6e73/axios.js?v=1756215744:2:4799
u/R/</<@https://xxx.com/cpresources/1e4a6e73/axios.js?v=1756215744:2:3877
p@https://xxx.com/cpresources/1e4a6e73/axios.js?v=1756215744:2:9964
s@https://xxx.com/cpresources/1e4a6e73/axios.js?v=1756215744:2:10204

[engram-design]

Thanks for the video, that's an interesting one - possible different though as it seems random.

Can you maybe shoot through a screenshot of your widget settings?

Firstly, the error message should be clearer than that, that's interesting to see. Is this on a non-devMode site? If you have a look in your /storage/logs/metrix-*.log file that should hopefully have a more detailed error, although that copyable error is supposed to be detailed too...

[diegocosta-dev]

Hi @engram-design Thank you for your attention to this. Yes, we are seeing this on the live site..

This issue is happening in "pages views" when selecting more recent dates, for example, the last 7 days.

Copied from Dashboard:

A server error occurred.
AxiosError: Request failed with status code 400
    at Ge (https://xxx.com/cpresources/1e4a6e73/axios.js?v=1756215744:2:31106)
    at XMLHttpRequest.v (https://xxx.com/cpresources/1e4a6e73/axios.js?v=1756215744:2:36220)
    at e.<anonymous> (https://xxx.com/cpresources/1e4a6e73/axios.js?v=1756215744:2:48189)
    at p (https://xxx.com/cpresources/1e4a6e73/axios.js?v=1756215744:2:3448)
    at Generator.<anonymous> (https://xxx.com/cpresources/1e4a6e73/axios.js?v=1756215744:2:4798)
    at Generator.throw (https://xxx.com/cpresources/1e4a6e73/axios.js?v=1756215744:2:3877)
    at p (https://xxx.com/cpresources/1e4a6e73/axios.js?v=1756215744:2:9964)
    at s (https://xxx.com/cpresources/1e4a6e73/axios.js?v=1756215744:2:10203)

More Context:

Pluging settings:

I am using the default settings.

Source:

I’m currently using Fathom Source

[engram-design]

Thanks for that, so that's still pretty odd about the error. For example, I can indeed see the issue on me end - clicking the "details" button:

Bad Request
Client error: `GET https://api.usefathom.com/v1/aggregations?entity=pageview&aggregates=pageviews&timezone=UTC&start_date=2025-08-30&end_date=2025-08-30&date_grouping=hour` resulted in a `400 Bad Request` response:
{"error":"Error with date_grouping: Hourly grouping is only supported for periods of up to 7 days."}

Fixed for the next release. To get this early, run composer require verbb/metrix:"dev-craft-4 as 1.0.2".

More to the point, though, it seems like I get this error with any widget when trying to render today's data. For example, a Line graph of today's data, which should be grouped hourly, throws that same error of Hourly grouping is only supported for periods of up to 7 days.. Of course, the dates are within 7 days, like 2025-08-30-2025-08-30 or even 2025-08-28-2025-08-30 - all have the same error. I think on that front, it might be an issue with their API.

[diegocosta-dev]

@engram-design

Thanks a lot for looking into this and for the quick fix!

Really appreciate the support and the clarification. 😄