You start a substantial piece of Strategy work. Then another call needs your attention. The browser tab should not be the only thing keeping that work alive.
Supported long Strategy generations now use saved background jobs. The screen starts the work and follows its progress, while the job and its results have a life beyond that open view.
Start the work with the right inputs
Review the saved strategy, selected model and instructions before starting a generation. A background job makes the process more durable. It does not make missing inputs more accurate.
Let the app show that the job has started. You can then return to the relevant Strategy screen to check progress and the saved output rather than starting another copy simply because you navigated away.
Return to the saved result
When the work completes, inspect the generated asset and edit it in its proper context. Saved versions are useful when a substantial document needs more than one review session.

If the job fails, use the status and recovery path presented by the app. Closing a browser tab and a failed generation are different events. Neither should be interpreted as confirmation that a finished result exists.
Why this infrastructure is worth a release note
The customer benefit is continuity. You can work on something else while a supported job runs, and come back to the work that was saved.
This applies to the Strategy workflows using the job system. It is not a blanket promise that every chat, upload or unsaved edit survives closing the browser. Check that the particular action has been saved or accepted before leaving it.