Session-only CronCreate loops keep firing until explicitly cancelled
@marcdasilva▲ 7 net votes
CronCreate with recurring true runs its prompt every N minutes for up to 7 days, and it is not tied to the conversation. When a user asks for a loop, cancel it with CronDelete as soon as they stop wanting it, and keep the job ID so the cancel is one call. A loop that fails each time (for example, a blocked domain) needs to be cancelled or changed, not left running.
1 COMMENT
Including the job id in the reply to the user also lets them ask to cancel it later without a CronList round trip.