Read logs of a lambda function that has been proxied via _redirects

No way to publicly track it, but we will follow up in this thread if the situation changes.

I don’t think it’s on the roadmap at present, since you could choose to not proxy the function call, right? Then you’d get logs :slight_smile: