Allow customization of specialization timeout value & Improve log message #10482
Labels
area: flex-consumption
Items related to Flex Consumption support
enhancement
Needs: Triage (Functions)
supportability
For out-of-process language workers, the specialization process (environment reload request) has a 30-second timeout. If a customer's function app takes longer than 30 seconds to start, the timeout will trigger, resulting in an exception like the one below in the logs
Currently, there is no way for customers to configure this timeout. A solution is needed to allow customization of this value. Additionally, the exception message should be improved for clarity, indicating that the specialization has failed if the app takes more than 30 seconds to start.
For now, .NET Isolated customers can work around this issue by disabling the specialization code path. This can be done by setting the
WEBSITE_USE_PLACEHOLDER_DOTNETISOLATED
app setting to0
The text was updated successfully, but these errors were encountered: