♻️ CI/CD | Fix Generate Commit Data Workflow

[tkapa]

Cc:

Hi

Pain

Build + Deployment workflows are being choked up by a failing piece of the GitHub Workflow.

A resource request Times out, causing the workflow to fail more often than not. Either the resource should be improved to cache the required responses, or we should be more lenient with the timeout.

What code could be improved?

.github/workflows

Tasks

• Investigate
• Fix

More Information

Screenshots

Thanks!

[babakamyljanovssw]

Update:

I did investigation on timeout failures of Azure function GetCommitHistorySyncHash in workflow runs:

• This function logic is pretty simple get string type value which is the last commit hash from Cosmos DB and return it to client, so there is no need to implement caching in the code as this function call usually takes a few seconds when it is successful.
• These timeouts happened before executing any function operations, so the code is not causing the timeouts.
• I think timeouts happened due to hitting monthly service limitations for Azure App Service Plan - https://learn.microsoft.com/en-us/azure/azure-functions/functions-scale#service-limits
• And Production workflow hasn't failed due to Azure function timeout since October 1st, 2024. The last time this function GetCommitHistorySyncHash timed out is on September 30th, 2024. So timeout failures stopped since October.
• The App Service Plan service limits are not per function individually, it is per Azure Function App. So I did checked which function is being used mostly and it is GetReactionsFunction, 30000 logs was returned since August 1st, 2024, due to most usage of this function, it has failed more with the timeout. I tested the reaction feature of rules page, and seems it is not working properly. All requests to GetReactionsFunction, ReactFunction, RemoveReactionFunction are giving CORS error from rules page. We might need new PBI for reaction feature to investigate it and handle this feature more properly

Figure: Liking and removing like are giving CORS error

[babakamyljanovssw]

Drafted issues raised after investigations of Azure Functions

#1556
#1557

[babakamyljanovssw]

Update:

The timeout failures of Azure Functions are not happening anymore in workflow runs

[babakamyljanovssw]

Since the timeout are not happening in recent workflows, I've sent email to myself to check this issue in one month if it is occurring again.

Email subject: Azure Functions - Timeout failures on workflows