Script Cooldown, Step Delay and Timeout: Which Clock Are You Changing?

A Script can be saved correctly and still be waiting for a reason. Before shortening a number, identify which clock it controls: starting the same Script again, advancing its current step, or expiring a run that has waited too long. These are separate decisions.

This reference builds on Scripts versus PPV workflows. It focuses on timing interactions and purchase locks, not choosing a workflow or finding media.

1. Cooldown is a reuse restriction, not the next-message timer

In the Script editor, Cooldown minutes controls reuse for the same fan. The current runtime also considers the Persona's strict Script cooldown, expressed in hours. It uses whichever is longer, with a minimum of one minute.

Fictional examples:

• Script cooldown 30 minutes and Persona cooldown 1 hour: the effective cooldown is 60 minutes.
• Script cooldown 360 minutes and Persona cooldown 1 hour: the effective cooldown is 360 minutes.
• Reducing the Script value from 30 to 10 minutes in the first example does not reduce the effective 60-minute restriction.

This is a duration calculation, not a promised restart time. An active run and a purchase lock can also prevent another start. The runtime can extend the cooldown when a run completes; do not assume it is always counted only from the original start.

2. Step delay and follow-up delay overlap; they are not added

A step has its own wait. For a follow-up step, the runtime also considers the Persona's follow-up delay. It uses the longer duration, measured from the execution's last advancement.

For example, a five-minute step wait and a one-minute Persona follow-up delay produce a five-minute timing threshold, not six minutes. A two-minute step wait and a ten-minute Persona follow-up delay produce a ten-minute threshold.

For a step that is not a follow-up, that Persona follow-up setting is not included in this particular calculation. Other eligibility checks still apply. Reaching the threshold means this timing guard no longer blocks the step; it does not prove a message was generated or delivered at that moment.

3. Timeout limits waiting; it does not schedule a send

Timeout minutes is the waiting window for an active run. The current runtime sets an expiry when the run starts and refreshes it after a sent step advances the run. When the expiry is reached, the expiry routine can mark the run expired.

A short timeout does not make a delayed step happen sooner. Review the timeout alongside the waits you intend to allow. A workflow configured to wait longer than its expiry window needs attention before activation; repeatedly restarting it is not a substitute for reviewing the configuration.

This guide does not establish the scheduler's exact execution cadence or a guaranteed wall-clock expiry time.

4. A purchase lock is different from a cooldown

The editor has a separate Lock this script after purchase control. The current start check looks for a recorded purchased media item associated with the same account, fan and Script. When the lock is enabled and such a record exists, it blocks another start of that Script.

Waiting for a numerical cooldown to finish does not remove that purchase-based condition. Before investigating a repeat offer, check whether the Script was intentionally configured not to restart after purchase. Do not disable this protection simply to make a troubleshooting attempt run.

A recorded purchase condition is not evidence of revenue attributable to this guide or a marketing campaign.

5. Check the account and Script before diagnosing the clock

In the normal start path, Scripts must be enabled for the account and the automation mode must permit Scripts. The Script itself must be active, and it must belong to the same account as the conversation. An existing active run can block a duplicate start independently of its cooldown.

These checks explain why changing a timing value alone may not address the reason a Script did not start. They are not an instruction to enable automation on a live account as a test.

Preactivation checklist

1. Confirm the intended account, automation mode and Script status.
2. Compare the Script cooldown in minutes with the Persona cooldown converted from hours.
3. For each follow-up, compare its step wait with the Persona follow-up delay; keep the longer one in your timing notes.
4. Review the timeout against the time the workflow needs to wait.
5. Decide whether the Script should remain locked after a recorded purchase.
6. Check for an existing active run before attempting another start.
7. Separate configuration, eligibility, send confirmation and purchase evidence in your review.
8. Validate with an authorized test workspace before making live changes. A read-only demo cannot demonstrate delivery.

If you need help, record the account and Script identifiers, the relevant timing values, the run state and the timestamp in your private support request. Do not publish fan messages or personal data in a community post.

Independent third-party tool; not affiliated with or endorsed by Fanvue. No live generation, purchase or delivery was performed for this reference.