There was a node/prefix SID renumbering operation across many L1 nodes in different areas. In total around 1000 nodes were involved in the change. Each one has one node SID and one prefix SID.
For a few routers, Juniper L1L2 device failed to reflect the SID change when leaking those prefixes from ISIS L1 area to ISIS L2 area.

For example:

Before the change on a L1 router:
- 10.10.10.10/32 node SID 808
- 10.11.11.11/32 prefix SID 111808

After the change:
- 10.10.10.10/32 node SID 1010
- 10.11.11.11/32 prefix SID 3010


L1 LSDB is fine, however Juniper L1L2 router doesn't reflect the change in L2:

IS-IS level 1 link-state database:
.....
    IP extended prefix: 10.11.11.11/32 metric 0 up
      14 bytes of subtlvs
      Administrative tag 1: 50
      Prefix SID, Flags: 0x20(R:0,N:0,P:1,E:0,V:0,L:0), Algo: SPF(0), Value: 808
...

IS-IS level 2 link-state database:
...
    IP extended prefix: 10.11.11.11/32 metric 0 up
      14 bytes of subtlvs
      Administrative tag 1: 11
      Prefix SID, Flags: 0xa0(R:1,N:0,P:1,E:0,V:0,L:0), Algo: SPF(0), Value: 111808      <<<<< incorrect (old) value

Workaround:

• Change SID values on the affected L1 node to a temporary unique numbers.
• Change the same SIDs back to target values