Request
Use private-address intent for both workers. Maintain the main at two OCPUs and 16 GB after its controlled stop, then leave the helper stopped.
Completion
Retain all reviewed settings and name the live guest, job and data checks still needed.
A fictional render cooperative needs a controlled local maintenance record for a main worker and a helper. Declare the main, stop it, save its reviewed Flex allocation and restart it. Then declare and stop the helper while retaining the main’s settings.
Each step carries the previous account. The stable generated identifiers are local training references from earlier responses; real operations must use their actual returned OCIDs. The browser doesn't boot workers or render an image. Finish by naming the guest, data-consistency and original-job checks needed to validate the real handoff. Keep configuration evidence separate from any unmeasured performance, availability or backup claim.