Why does the new deployment slot from a production slot of my Function App show 'Runtime version is Error'?

Davies Nurudeen Adedeji 5

I recently created a new deployment slot from an existing production slot in my Azure Function App, but the new slot is displaying an error stating that the runtime version is invalid. How can I resolve this issue and ensure the new slot is configured correctly with the appropriate runtime version?And is the runtime version error the reason I am unable to deploy into the slot?

Khadeer Ali 2,945 Reputation points Microsoft Vendor

2025-02-04T10:58:26.28+00:00

@Davies Nurudeen Adedeji ,

Thank you for your patience and for sharing your feedback on the Q&A community platform.

We noticed that your recent experience was rated low (Answer provided was not helpful). We truly value your input and would like to understand how we can improve to make your experience a positive one. Could you please tell us what we could have done better to assist you effectively with the "Runtime version is Error" issue in your Function App deployment slot? Specifically, were there any steps that were unclear, or was there information missing that would have helped you resolve the problem?

We are here to help and strive to provide the best support possible. Your feedback is incredibly important to us, and we are committed to making your experience better.

If you have any additional questions or need further assistance, please don’t hesitate to let us know—we’re more than happy to help!

We would greatly appreciate it if you could consider re-surveying for the engagement you received on the thread after we've had a chance to address your concerns. Your feedback is invaluable in helping us improve and better serve the community.
References:
Troubleshoot common issues during Azure Runtime upgrade

1 answer

Abiola Akinbade 23,060 Reputation points

2024-08-09T08:37:14.3+00:00
The runtime version error is likely preventing deployments. it usually when there's a mismatch between the expected runtime version and the one configured for the slot.

I will recommend you compare the FUNCTIONS_EXTENSION_VERSION setting in both slots and check if thery are valid versions.

You can try CLI similar to below and replace appropriately.

az functionapp config appsettings set --name <app-name> --resource-group <resource-group-name> --slot <slot-name> --settings FUNCTIONS_EXTENSION_VERSION=~4

**
You can mark it 'Accept Answer' and 'Upvote' if this helped you**

Regards,

Abiola
Please sign in to rate this answer.
Davies Nurudeen Adedeji 5 Reputation points

2024-08-09T08:46:53.13+00:00

Thank you Akinbade, I have compared the FUNCTIONS_EXTENSION_VERSION setting in both slots they are both ~4 infact they both share identical App Settings. I think it would be more helpful if you also try it out on your Azure portal:

Create a function App is west Europe on Standard S1 app service plan

Go to Deployment slots in the left hand menu and "Add slot"

It will only request for a name eg "staging" then check the slot if the Runtime version shows.

Thanks once again

Jaya Krishna Mandivarapu 0 Reputation points Microsoft Employee

2025-01-17T17:24:26.5566667+00:00

can I know the answer to this? I am also facing the same issue for azure function app under elastic premium plan
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Why does the new deployment slot from a production slot of my Function App show 'Runtime version is Error'?

1 answer

Your answer