Constant Epoch errors
Hi,
Are these errors normal when running an EventHub Function trigger? Would it be possible to downgrade these errors to info if it's normal and if they happen frequently? As they litter the AppInsights.
I have checked in the past and if I am not mistaken this is normal, but it has been years ago that I posted this question and it seems they are still there.
Error Message: 'New receiver 'P7-533b391b-13e7-4bd2-923a-460f7d0e7b2b' with higher epoch of '0' is created hence current receiver 'P7-4250cb06-bded-4080-9b6a-948f81ea1924' with epoch '0' is getting disconnected. If you are recreating the receiver, make sure a higher epoch is used. TrackingId:1a808ca2000039e7001b239f625dabd4_G36_B40,
Hi @grik001 , Thank you for your feedback! We will check for the possibilities internally and update you with the findings.
Hi @v-bbalaiagar any updates on this?
We just recently upgraded a dotnet core 3.1 azure function to dotnet 6 and started seeing this error in the logs.