Hi @sanofip , are you generating the number in the application provisioning policy? If it is a field value rule, it may be evaluated multiple times before provisioning which is why you may see the jump of 2 or 3 numbers. If you have a rule that does it can you share the logic?
This suggests that the rule is being called several times in a row. If you add logging to your rule, does the code appear to be running more than once?
This can happen sometimes with the Create and Update provisioning policies, if the ProvisioningPlan ends up being compiled twice. It would probably be good to test the value of ‘current’ in your rule and just return the existing value if it’s non-null.
Yet the create provisioning policy rule calling many times and every time it is increasing the sequence number, and we are using the custom object to save the application name and its previous sequence number. So, every time the rule executes the custom object getting invoked and increasing its sequence number. I tried by adding some variable like executed to plan/ plan attributes to check whether it is already executed to restrict to execute the rule again, but it is not success.