@Rafael José S. da Costa Thanks for your patience on this.
This is a known issue Our Engineering team are actively working on a fix and currently we don't any ETA at this moment. I will update your here accordingly once I have any updates on this.
And the possible workaround is to add the app setting FUNCTIONS_EXTENSION_VERSION
value as 4.837.1.23604
to fix the issue.
Hope this helps, let me know if you have any further questions on this.