DigLab

Use ↓ ↑ to browse results, Enter to open, Esc to close.

Space posts with cooldowns

Set a minimum gap for an account and resolve schedule conflicts.

Posting cooldowns help keep several posts from landing too close together on the same account. They are different from a delay between destinations within one publishing action.

Configure an account

  1. Open Settings → Cooldowns where available.

  2. Find the exact connected account and choose a minimum gap, or a custom interval if offered.

  3. Save the setting and review how upcoming posts fit around it.

  4. Check the final resolved time when scheduling through a queue or automation as well as the composer.

Resolve a conflict

When a new time falls inside a cooldown window, the interface may offer to move it to the next allowed slot, override the restriction or cancel scheduling. Read the proposed time before accepting it. Use an override only for a deliberate exception. It can cause closely spaced posts even when the normal account policy prevents that. Check the schedule afterward so a teammate understands what will happen.

Troubleshoot unexpected spacing

Check the account's cooldown, the queue's timezone and slot grid, and any other posts near the intended time. A changed resolved time may be the expected result of respecting the gap. If the final scheduled time still violates the configured interval, record the two post identifiers, times, timezone and error details for support. Do not repeatedly reschedule a batch until the cause is understood.

Browse all DigLab docs →

DigLab Social · Practical product guides

DigLab