Correlation Rule include Correlation Extractor and Correlation Replacement,but after Correlation Wizard, Correlation Replacement is disappeared.

[twfish66]

Describe the bug

Issue1: Correlation Rule include Correlation Extractor and Correlation Replacement,but after Correlation Wizard, Correlation Replacement is disappeared. In suggestions screen,Only show Obtained from ,but no Used on data.
Issue2: In Suggestions Panel,Click on Apply button,but in the test plan, I can see the new regular Expression Extrator.

Environment
windows 11 and windows 10
apache-jmeter-5.6.3
BlazeMeter - Auto Correlation Recorder Plugin(2.6)

To Reproduce

Steps to reproduce the bug:

1. Click on bzm-Auto Correlation Recorder
2. Click on 'Correlation' tab
3. Click on 'open suggestion panel' tab
4. Click on 'replay recording' button.
5. After replaying
6. Click 'Yes'
7. Select 'Existing Correlation Templates'
8. Click Continue
9. choose draft[ ],and select apache-jmeter-5.6.3\bin\Replay\replay-1726472954788.jtl(It's the step4 replay jtl)
10. Click Continue and ok
11. In Suggestions panel,see Source:'twfish(local),Name:XSRFTOKEN,obtained from((1) 001 /cfi/),Used on (0)
12. Save Correlation rules
13. Go back Correlation tab
14. One new rule is add,reference Variable:XSRFTOKEN,Correlation Extrator:Regex/Set-Cookie: XSRF-TOKEN=(.+?); ,Correlation Replacement:Null
15. Issue 1:But Original my twfish rule Correlation Replacement is Regex/X-XSRF-TOKEN: ([^&\\n]+), not null
16. Issue2: goto step 7 ,click on Apply button,but in the test plan, I can see the new regular Expression Extrator.

Expected behavior

A clear and concise description of what you expected to happen.

Complementary information

To have a faster and accurate response to your issue, please share:
Issue about Jmeter correlation rule20240916.docx
Issue mail data.zip

• The JTL for the recording and the replay (if needed)
• The configuration of the Correlation Rules/Templates used (picture, test plan, or JSON file)

In case of sharing the JTL, please make sure you configure it as shown in the docs/JTLRecordingConfiguration.png file

Additional context
Add any other context about the problem here.