Exponential Backoff Retries Inconsistent.

[Gamecock]

Check for a solution in the Azure portal

When running a functionapp on a consumption plan, exponential backoff does not provide full number off retries.

Investigative information

Please provide the following:

• Timestamp: 2024-02-22 18:39:59.998
• Function App version: ~4
• Function App name: mike-retry-test
• Function name(s) (as appropriate): ExponentialBackoffSample
• Invocation ID: 50203b9ccae58b539320ff956040fbe0
• Region: USEast

Repro steps

Provide the steps required to reproduce the problem:

Deploy and run function with retry

Expected behavior

Initial Attempt and then 5 retires.

Actual behavior

Locally 1 Attempt and 4 Retries This could be considered design intent if everything worked this way and it was documented. Consumption 1 Attempts and 3 Retries But sometimes 4 Retries

AppService - Works as expected ElasticPremium - Works as expected.

Known workarounds

Increase Retries.

Related information

Provide any related information

• Programming language used
• Links to source https://github.com/Gamecock/FunctionSample
• Bindings used Timer Trigger
  Source

        [Function("ExponentialBackoffSample")]
        [ExponentialBackoffRetry(5,"00:02:00", "1:00:00")]
        public void Run([TimerTrigger("0 40 */2 * * *")] MyInfo myTimer)
        {
            _logger.LogInformation($"C# Timer trigger function executed at: {DateTime.Now}");
            _logger.LogInformation($"Next timer schedule at: {myTimer.ScheduleStatus.Next}");
            throw new Exception("Testing Backoff");
        }

-->

[bhagyshricompany]

Thanks for repro will check and update.

[bhagyshricompany]

seems your deployed function have issues for Exception encountered while listening to EventStream An existing connection was forcibly closed by the remote host. 2/29/2024 12:04:03 PM. you can refer this. https://learn.microsoft.com/en-us/answers/questions/965564/how-to-solve-an-existing-connection-was-forcibly-c

[Gamecock]

Thanks, where do you see the exception? Also, the article does not seem relevant, as of have limited to more control of the configuration of the socket connection.

On Fri, Mar 1, 2024, 2:14 AM bhagyshricompany @.***> wrote:

seems your deployed function have issues for Exception encountered while listening to EventStream An existing connection was forcibly closed by the remote host. 2/29/2024 12:04:03 PM. you can refer this.

https://learn.microsoft.com/en-us/answers/questions/965564/how-to-solve-an-existing-connection-was-forcibly-c

— Reply to this email directly, view it on GitHub https://github.com/Azure/azure-functions-host/issues/9892#issuecomment-1972632792, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMSCSQ5ADUKBVMYZRK27T3YWATDXAVCNFSM6AAAAABDVTTTI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSGYZTENZZGI . You are receiving this because you authored the thread.Message ID: @.***>

[bhagyshricompany]

@fabiocav pls comment and validate.Thanks