{"id":"data-transfers.every-n-hours-timing","url":"/faq/data-transfers/every-n-hours-timing","category":{"id":"data-transfers","title":"Data Transfers"},"subcategory":{"id":"scheduling","title":"Scheduling transfers"},"question":"When does an “Every N hours” transfer run?","alt_questions":["every 6 hours schedule timing","hourly transfer schedule","every N hours starts when","how often can a transfer run","run a sync every hour"],"short_answer":"Every N hours (1–24) counted from the previous run, starting with an immediate first run — not fixed clock times. A run still in progress causes the next to be skipped. Use Daily for fixed times.","answer_markdown":"It runs every N hours (1 to 24) counted from its previous run — the first run happens as soon as you click **Start Transfer**, and each later run comes N hours after the last one started. It isn't tied to the clock, so a 6-hour schedule started at 10:20 runs around 16:20, 22:20 and so on.\n\nIf a run is still going when the next is due, the next is skipped rather than piling up. If you want runs at fixed times of day, use **Daily** instead.\n\nRelated: [Schedule a transfer](/faq/data-transfers/schedule-a-recurring-transfer) · [Why was a run skipped?](/faq/data-transfers/why-was-a-scheduled-run-skipped)","answer_html":"

It runs every N hours (1 to 24) counted from its previous run — the first run happens as soon as you click Start Transfer, and each later run comes N hours after the last one started. It isn't tied to the clock, so a 6-hour schedule started at 10:20 runs around 16:20, 22:20 and so on.

\n

If a run is still going when the next is due, the next is skipped rather than piling up. If you want runs at fixed times of day, use Daily instead.

\n

Related: Schedule a transfer · Why was a run skipped?

","answer_text":"It runs every N hours (1 to 24) counted from its previous run — the first run happens as soon as you click Start Transfer, and each later run comes N hours after the last one started. It isn't tied to the clock, so a 6-hour schedule started at 10:20 runs around 16:20, 22:20 and so on.\n\nIf a run is still going when the next is due, the next is skipped rather than piling up. If you want runs at fixed times of day, use Daily instead.\n\nRelated: Schedule a transfer · Why was a run skipped?","tags":["schedule","hourly","timing"],"related":[{"id":"data-transfers.schedule-a-recurring-transfer","question":"How do I schedule a transfer to run automatically?","url":"/faq/data-transfers/schedule-a-recurring-transfer"},{"id":"data-transfers.why-was-a-scheduled-run-skipped","question":"Why didn't a scheduled transfer start at its usual time?","url":"/faq/data-transfers/why-was-a-scheduled-run-skipped"}],"applies_to":"all","last_reviewed":"2026-10-01","title":"When does an “Every N hours” transfer run? — Storage Studio FAQ","description":"Every N hours (1–24) counted from the previous run, starting with an immediate first run — not fixed clock times. A run still in progress causes the next to be skipped. Use Daily for fixed times.","crumbs":[{"name":"Home","path":"/"},{"name":"FAQ","path":"/faq/"},{"name":"Data Transfers","path":"/faq/data-transfers/"},{"name":"When does an “Every N hours” transfer run?","path":"/faq/data-transfers/every-n-hours-timing"}],"jsonld":{"@context":"https://schema.org","@type":"FAQPage","url":"https://storagestudio.us/faq/data-transfers/every-n-hours-timing","inLanguage":"en","dateModified":"2026-10-01","mainEntity":[{"@type":"Question","name":"When does an “Every N hours” transfer run?","alternateName":["every 6 hours schedule timing","hourly transfer schedule","every N hours starts when","how often can a transfer run","run a sync every hour"],"acceptedAnswer":{"@type":"Answer","text":"It runs every N hours (1 to 24) counted from its previous run — the first run happens as soon as you click Start Transfer, and each later run comes N hours after the last one started. It isn't tied to the clock, so a 6-hour schedule started at 10:20 runs around 16:20, 22:20 and so on.\n\nIf a run is still going when the next is due, the next is skipped rather than piling up. If you want runs at fixed times of day, use Daily instead.\n\nRelated: Schedule a transfer · Why was a run skipped?","url":"https://storagestudio.us/faq/data-transfers/every-n-hours-timing"}}]},"fragment":"
\n
\n\n\n\n\n
\n
\n

Data Transfers · Scheduling transfers

\n

When does an “Every N hours” transfer run?

\n

Short answer: Every N hours (1–24) counted from the previous run, starting with an immediate first run — not fixed clock times. A run still in progress causes the next to be skipped. Use Daily for fixed times.

\n

It runs every N hours (1 to 24) counted from its previous run — the first run happens as soon as you click Start Transfer, and each later run comes N hours after the last one started. It isn't tied to the clock, so a 6-hour schedule started at 10:20 runs around 16:20, 22:20 and so on.

\n

If a run is still going when the next is due, the next is skipped rather than piling up. If you want runs at fixed times of day, use Daily instead.

\n

Related: Schedule a transfer · Why was a run skipped?

\n\n

Last reviewed

\n\n

Related questions

\n

Also available as Markdown and JSON.

\n
"}