Sending is paused: restrictions and how to resume
The red bar
If a platform shows a restriction on your account, DM Commander stops sending on that platform straight away and puts a red bar across the top of every page. It reads:
"⛔ Sending on <Platform> is paused — <Platform> showed a restriction on your account (browser profile "X") on <date>: '<platform's own words>'. Give it 24–48 hours, then resume. Reply checking and Account Warm-Up keep running."
Next to it is a white button: Resume sending.
The platform's own wording is quoted inside the bar, so you can see exactly what it said. The browser profile is named if you have set up profiles, so you know which account it was. The pause applies to that platform only — your other platforms keep sending.
What triggers it
Only the platform's own restriction notice about your account. DM Commander recognises those notices automatically while a run is in progress and stops sending there and then.
What does not trigger it
A notice about one recipient is not a restriction on you, and it never pauses anything. Only that one lead is skipped and the run carries on. You will see reasons like these in the log instead:
- "<name> cannot be messaged (deleted, suspended or not found), so they were skipped."
- "<name> does not accept messages from you on X, so they were skipped."
- "The profile of <name> has no Message button."
The run ends honestly
When a restriction is spotted mid-run, the run stops and reports what actually went out, not what it intended to send. The number in your log is the real number. Nobody gets messaged twice because of it.
What keeps running
- Step 3 · Catch Replies — replies are still collected, so a reply that arrives during the pause still reaches you.
- Your Inbox — drafting, editing and approving all still work. Approved messages simply wait.
- Follow-up queuing.
- Account Warm-Up (New Accounts) — so the account keeps looking normally active while it rests.
- Every other platform.
How to resume
- Wait 24 to 48 hours. Use the account normally in the meantime if you like — browse, reply to real people, behave like yourself.
- Open your dashboard. The red bar is on every page.
- Click Resume sending. The button changes to "Resuming…" and the bar disappears.
- Sending picks up on that platform from the next check.
If the restriction has already cleared by itself, you will see "Nothing to resume." That is good news, not an error — there was nothing left holding you back.
Resuming is manual on purpose. Nothing restarts behind your back, so you decide when the account has had long enough.
What to do differently afterwards
Treat it as the platform asking for a slower pace, and come back lighter:
- Lower Max / Day on that platform on Deploy Agents, and build it back up over a week or two.
- Leave the "Override the auto safety cap" checkbox unticked so the automatic cap is in charge.
- Switch on Account Warm-Up (New Accounts) for that platform if it is not on already.
- Check your first messages contain no links. Links belong in replies and follow-ups, wherever {link} appears.
- Run one campaign on that social account for a while rather than several at once.
Reading what happened
Open Agent Activity Log in the sidebar and click the run. The row expands and shows Why it failed, with the platform's own words and a What to try: line. For a restriction it reads: "Give it 24 to 48 hours, then press Resume on your dashboard."
If the wording on your bar does not look like anything above, send it to support@hustlegrow.com and the team will take a look. You can also search the rest of the help centre at https://helpdesk.hustlegrow.com/.
Next step
While you wait out the 24 to 48 hours, open Deploy Agents and switch on Account Warm-Up (New Accounts) for that platform, so the account keeps building history and is in better shape when you press Resume sending.