Twice restarts required

Mansi Gusain 495 Reputation points
2025-03-10T12:11:53.3166667+00:00

Hey, I have a yaml file, to which if I make the changes and save, firstly it gets generated in the local and then it is uploaded to the fileshare in the storage account.

I have checked everytime the newly local file with all the changes I require is generated and the same is uploaded in the file share also.

Now the issue is that if I restart the application for which i needed the yaml then the changes do not appear i have to restart twice.

I have redis from which I clear the cache.

The file uploaded always has the changes. But not reflected in the UI until twice the restart.

The health probes config is as

User's image

User's image

User's image

Azure Container Apps
Azure Container Apps
An Azure service that provides a general-purpose, serverless container platform.
691 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Mansi Gusain 495 Reputation points
    2025-03-17T06:10:45.5533333+00:00

    Hi thanks for replying I found the solution to it.

    Stopping the container and then applying yaml changes. Then starting the container and restarting the application.

    0 comments No comments

  2. Pravallika Kothaveeranna Gari 955 Reputation points Microsoft External Staff Moderator
    2025-03-17T08:16:54.0166667+00:00

    Hi Mansi Gusain, I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

    Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

    Issue:

    The changes made to the YAML file are not reflected in the UI until the application is restarted twice, despite the updated file being uploaded correctly.

    Solution:

    This could be due to caching issues or delays in the application detecting the updated file after the first restart.

    It turned out the issue can be resolved by following below steps:

    1. Stop the container to ensure the application completely halts and releases the memory references or locks that it may have on the YAML file or cached data.
    2. Make the necessary changes to the YAML file and upload it to file share where the application reads from.
    3. Start the container again to ensure the application starts fresh and loads the updated YAML file with no old versions of the file or cache into memory.
    4. Restart the application to reload the configuration fully. This is to make sure the changes gets reflected in the application's runtime.

    Hope this helps.

    Please remember to "Accept Answer" if the sol has helped, so that others in the community facing similar issues can easily find the solution.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.