I think this issue with your Azure Function App, which is blob-triggered, might be related to the idle state behavior of the Consumption plan.
When hosted on a Consumption plan, function apps can go idle after periods of inactivity to conserve resources, which can delay triggers. The fact that the function sometimes triggers after you check metrics in the Azure portal suggests that this wakes up the app, aligning with this behavior.
If the function app was working as expected until 10 days ago but now triggers only intermittently, it could be linked to changes in underlying infrastructure, storage account configuration, or potential scaling issues with the Consumption plan.