Failsafe mechanisms to mitigate outages in the authoritative source that lead to role deprovisioning

I do not agree with your point here, my point here is the calculation of an Identity Attribute has no order, so if in the next aggregation your critical_attribute1 is calculated first and then your static transform on the other attribute runs, it should not be storing your previous value, it should be storing your new value not the previous value, the explanation of calculation of identityAttribute doesn’t matter when there’s no particular order by which an identityAttribute is calculated.