Hello,
I've found two errors with graph protoypes when we are using macro like:

{$VFS.FS.PUSED.MAX.CRIT:regex:"^/home$"}

1. as it's shown on screenshot (02-07.03.2025.png), graph was added - but data is not visible on graph it self, it's only visible on right corner, so clear values from item,

Graph configuration is "default" from most recent 7.0LTS "Linux by zabbix agent" template, and "Mounted filesystem discovery" discovery rule,

2. i've found that if for example host does have macro like:

{$VFS.FS.PUSED.MAX.CRIT:regex:"^/zabbix.com$"}

In general with path which does not exist on monitored system, both item and trigger is not created,
But graph prototype does work, and it adds graph which is not visible due to PHP error (see 1-07.03.2025.png)

This is shown when we go to "

FS [\{#FSTYPE}(\{#FSNAME})]: Space usage graph, in % (relative to max available)"

graph protoype, and we click on "preview"
But it's also visible from latest data view, when we click on "graphs" and host graphs are shown,

To reproduce, add macro which is used later in any of discovery rule, so for example this:

{$VFS.FS.PUSED.MAX.CRIT:regex:"^/home$"}

But in regex add path which does not exist on system (check with "lsblk" for example),

Discovered on Zabbix 7.0.9 (RHEL9, Nginx 1.20, php-fpm 8.2.25, pgsql 17.3&tsdb2.17)