Posting Cooldowns

What cooldowns are for

The fastest way to get an account rate-limited (or shadow-banned) is to publish 5 posts to the same platform in 10 minutes. Cooldowns enforce a minimum gap between posts on each account — so even if your queue, automation, or Bulk Fill wants to fire rapid-fire, Aidelly spaces them out.

Cooldowns are platform-aware: a 6-hour Instagram cooldown and a 30-minute X cooldown can coexist on the same connection set.

How is this different from "Scheduled post delays"?

Cooldowns are the meaningful protection. Scheduled delays are a low-level safety net.

How to access

1. Open Settings → Cooldowns.
2. The page lists every connected account grouped by platform.

Step 1 — Set a per-account cooldown

1. Find the account in the list.
2. Pick a cooldown from the dropdown: None, 15 min, 30 min, 1 hour, 3 hours, 6 hours, 24 hours, or Custom.
3. Save.

The cooldown takes effect immediately for any new post you queue.

Sensible defaults: Instagram 4–6 hours, X 30 min, LinkedIn 2 hours, TikTok 6 hours. These are not platform-enforced limits — they're algorithmic-friendly cadences.

Step 2 — Schedule conflict warnings

When you schedule a post inside the cooldown window of the previous post on the same account, Aidelly catches it at schedule time and shows a banner:

"This post is 1h 12min after the last Instagram post — within your 4-hour cooldown. Choose what to do:"

Three options:

1. Slide to next legal slot — Aidelly automatically rolls the post forward to the earliest time that respects the cooldown.
2. Override — publish anyway. Confirms with a second click since this is a deliberate exception.
3. Cancel — don't schedule.

Step 3 — Per-post override

You can also override at the composer level for one-off campaign moments:

1. In the composer, expand Advanced scheduling.
2. Toggle Override account cooldown for this post.
3. Schedule.

The saved cooldown stays unchanged — only this specific post bypasses it.

Cooldowns + automations

Automations, Bulk Fill, and RSS auto-post all respect cooldowns. When a bulk run would produce conflicts, it stretches the schedule forward in time to fit the cooldown gap rather than firing everything at once.

Cooldowns + Posting Sets

A Posting Set can carry a cooldown override so one preset (e.g. an event-day campaign) ignores the default cooldown while the rest of your scheduling respects it.

Common patterns

Related guides

• Content Calendar — cooldown gaps render as a visual indicator on the calendar.
• Bulk Fill — bulk runs respect cooldowns automatically.
• Posting Sets — per-preset cooldown overrides.