@srinit Yes, you can move the Initialization Stage logic to the Primary Stage, especially if you need auto-save to work during early data entry. Keep the new Initialization Stage minimal just system-level setup like setting pyLabel, routing, or setting default values. This change is generally safe but test it well with existing cases. For in-flight cases, make sure they don’t break due to stage mismatch; consider locking old cases or using a when rule to skip the new Initialization Stage. Backup your app before the change and test it in lower environments first. Others have done this successfully, so it’s a common workaround.