loop-local-runtime-note

Local loops run only until the current session closes and do not persist beyond it. For durable cloud-based loops that continue running after the session ends, use the /schedule_ command instead.

To keep loops running after the session ends, use the /schedule_ command for durable cloud-based loops. Local loops terminate automatically when the current session closes, so they are not suitable for persistent tasks.

Local loops run only until the current session closes, while durable cloud-based loops persist beyond the active session. You create durable loops using the /schedule_ command instead of relying on local loop execution.

Use /schedule_ instead of a local loop when your task needs to persist beyond the current session. Local loops stop running when the session closes, making /schedule_ necessary for any durable, cloud-based loop requirement.

Local loops stop running when the session closes because they are not designed to persist. To avoid unexpected loop termination, use /schedule_ to create durable cloud-based loops that continue after the session ends.

Yes, you can append a conditional confirmation note informing users that local loops run until the session closes. If a cloud-offer question was already shown, omit the note; otherwise, display the italicized line recommending /schedule_.