feat: considerations app configuration

actions/com.steadybit.extension_azure.app_configuration.exception/summary.mdx

@@ -22,6 +22,12 @@ ASP.NET application must use .NET 8 or higher.
 
 ASP.NET application must [be wrapped with the Steadybit Injection Middleware](https://github.com/steadybit/failure-azure-functions-net).
 
+## Important Considerations
+
+The default implementation of the Azure App Configuration middleware in .NET is non-blocking. Therefore, the configuration refresh
+does not occur in the request where refresh started; instead, it is active from that request onward.
+In Azure Functions, this might present itself as flaky due to how the Azure Function Consumption Plan operates, which reuses instances with the previous state (you need one request beforehand to get the refreshed configuration).
+
 # Parameters
 
 | Parameter | Description                                                                       | Default |

actions/com.steadybit.extension_azure.app_configuration.fill_disk/summary.mdx

@@ -22,6 +22,12 @@ ASP.NET application must use .NET 8 or higher.
 
 ASP.NET application must [be wrapped with the Steadybit Injection Middleware](https://github.com/steadybit/failure-azure-functions-net).
 
+## Important Considerations
+
+The default implementation of the Azure App Configuration middleware in .NET is non-blocking. Therefore, the configuration refresh
+does not occur in the request where refresh started; instead, it is active from that request onward.
+In Azure Functions, this might present itself as flaky due to how the Azure Function Consumption Plan operates, which reuses instances with the previous state (you need one request beforehand to get the refreshed configuration).
+
 # Parameters
 
 | Parameter | Description                                                                       | Default |

actions/com.steadybit.extension_azure.app_configuration.latency/summary.mdx

@@ -22,6 +22,12 @@ ASP.NET application must use .NET 8 or higher.
 
 ASP.NET application must [be wrapped with the Steadybit Injection Middleware](https://github.com/steadybit/failure-azure-functions-net).
 
+## Important Considerations
+
+The default implementation of the Azure App Configuration middleware in .NET is non-blocking. Therefore, the configuration refresh
+does not occur in the request where refresh started; instead, it is active from that request onward.
+In Azure Functions, this might present itself as flaky due to how the Azure Function Consumption Plan operates, which reuses instances with the previous state (you need one request beforehand to get the refreshed configuration).
+
 # Parameters
 
 | Parameter       | Description                                                                       | Default |

actions/com.steadybit.extension_azure.app_configuration.status_code/summary.mdx

@@ -22,6 +22,12 @@ ASP.NET application must use .NET 8 or higher.
 
 ASP.NET application must [be wrapped with the Steadybit Injection Middleware](https://github.com/steadybit/failure-azure-functions-net).
 
+## Important Considerations
+
+The default implementation of the Azure App Configuration middleware in .NET is non-blocking. Therefore, the configuration refresh
+does not occur in the request where refresh started; instead, it is active from that request onward.
+In Azure Functions, this might present itself as flaky due to how the Azure Function Consumption Plan operates, which reuses instances with the previous state (you need one request beforehand to get the refreshed configuration).
+
 # Parameters
 
 | Parameter   | Description                                                                       | Default |