M22 Issue - LegalTag expiration/deletion process
I tested yesterday/today for the legal tag expiration/deletion scenarios in AWS/AZURE M22 pre-shipping environments and sharing the test results here:
AZURE:
(1) The legal tag expiration job is not running. I created a legaltag yesterday that should be expired today. But I am not seeing the legal tag set to INVALID today. After I manually ran the legal tag expiration job (from api call in postman), the legal tag is set to INVALID.
(2) When the legal tag is set to INVALID by the legal tag expiration job, I am still able to see the associated data record with Storage service api and Search service api. Seems there is no trigger happening.
(3) When I deleted a legal tag, I am still able to see the associated data record with Storage service api and Search service api. Seems there is no trigger happening.
AWS:
(1) The legal tag expiration job is running. I created a legaltag yesterday that should be expired today. And the legal tag is set to INVALID today as expected.
(2) When the legal tag is set to INVALID by the legal tag expiration job, I am no longer able to see the associated data record with Storage service api and Search service api as expected.
(3) When I updated the legal tag with a future expiration date, I am still not able to see the associated data record with Storage service api and Search service api. There is no trigger happening when the legal tag is updated. But after the legal tag expiration job is run, I am able to see the associated data record with Storage service api and Search service api as expected.
(4) When I deleted a legal tag, I am no longer able to see the associated data record with Storage service api and Search service api as expected. But when I recreated the legal tag, I am still not able to see the associated data record with Storage service api and Search service api (even after the legal tag expiration job is run). Seems there is no trigger happening when a legal tag is recreated.