Back to journal

Publish a profile after the whole save succeeds

On September 7, I worked on the order of operations when a mobile profile is saved in Seasonal.Work. A profile can contain related information that needs more than one write. Completing the first write does not necessarily mean the complete profile is ready to be public. The correction makes that intermediate state part of the save sequence.

During the relevant relation repairs, the profile remains private. The sequence restores the intended publication state only after the complete save succeeds. This connects publication to the outcome of the whole operation, rather than allowing an earlier step to stand in for the final result. It also preserves the difference between a person wanting a public profile and the application having finished preparing that profile for publication.

The important boundary is the failure case. If the sequence stops before the required work is complete, the code should not proceed as though the final publication step has been earned. A partially completed save and a completed public profile are different outcomes. Making that distinction explicit in the shared mobile save path keeps it close to the operation that knows whether its steps succeeded, instead of leaving each screen to infer readiness from a partial result.

The implementation and its regression coverage were merged on September 7. The original release record still treated device flows and protected rollout as separate acceptance gates. I therefore describe this as a completed code safeguard, not a new verification on a person's phone or evidence that a particular profile was published. The useful public lesson does not require revealing profile contents or internal sensitive-data rules: public visibility should follow the successful completion of the work that makes the profile ready.

Reflection

Saving and publishing can share a button without being the same operation. Seasonal.Work's change keeps the publication decision behind the complete save, so an intermediate technical success cannot become an unintended public outcome.