Hey @David_Arbias, you’re reading the current behaviour correctly. Scope requirements are calculated from the Function’s full input query, rather than whether a field was used by a particular feature or invocation. That means including product fields causes read_products to be required for viewing every run from that Function on the shop.
The Function still should execute normally, but I agree this creates a poor debugging tradeoff and can encourage apps to request broader permissions than they otherwise need, I’ll pass along this feedback on my end.
If you see the same message where read_products is already granted or where the input query doesn’t select product data, just send me a fresh invocation and we’ll treat that separately as a possible issue for sure.
We’re also facing significant issues here with debugging functions.
We don’t need to see the PII data in the log, and don’t want to apply for protected customer data access as we only need to debug these requests for a very small handful of merchants.
However, the current way the permissions are restricted, means we can’t see any log information, previously when the PII data was simply truncated this still allowed us to effectively support our functions based apps.
Can this functionality be brought back please?
Just to add to this, when viewing logs for our own dev stores, the PII info IS redacted.
Today I found out that if you end up having 1 million error runs in your dashboad, there’s nothing you can do to help your users, except unnecessarily ask for every possible permission to debug your functions.
