Some path filters depend on an availability context, which isn't available by the time we get to the action itself. This means we can't check those path filters when consuming the path, which means some issues with rogue traces might not be caught.
This isn't a bug per se, as that filter check is just a safeguard, but it's annoying nonetheless.
Some path filters depend on an availability context, which isn't available by the time we get to the action itself. This means we can't check those path filters when consuming the path, which means some issues with rogue traces might not be caught.
This isn't a bug per se, as that filter check is just a safeguard, but it's annoying nonetheless.