Custom headers issue on two different hosting environments

[CCGRegaltest]

Before opening, please confirm:

• I have checked to see if my question is addressed in the FAQ.
• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

App Id

arn:aws:amplify:ap-northeast-1:476944795571:apps/d33dvg9x53pe0j

AWS Region

ap-northeast-1

Amplify Hosting feature

Custom domain

Frontend framework

Other

Next.js version

N/A

Next.js router

N/A

Describe the bug

My app has 2 environments. One is "main" (for production) and the other one is "staging".
After I created a new custom header by edit the customHttp.yml on AWS portal UI, main will auto take effect immediately about the new headers while staging will take effect until the app be redeployed.
Why there are difference between two environments?

Expected behavior

Both should need redeploy to let them taking effect the new headers.

Reproduction steps

1. Create new custom headers in AWS Amplify console and Save.
2. Staging environment takes effect while main will not.

Build Settings

No response

Log output

N/A

Additional information

N/A

[mauerbac]

Are you able to open a support case so we can look at the exact details of your app? Thank you

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

[github-actions]

This issue has been automatically locked.