Scheduling & Publishing
Testing connections before you publish
The connection check that runs before a post goes out, what a failure means, and when to continue anyway.
Last updated September 2, 2026
Before publishing, Gorilla Dash verifies that it can still reach each channel you selected. It takes a moment and it catches the most common cause of a failed post: a connection that lapsed since you last used it.
What the result means
| Result | Means |
|---|---|
| Verified | The channel answered. Publishing should work. |
| Connection failed | Gorilla Dash could not reach it. The post will very likely fail on that channel. |
| No response for platform | The platform did not answer in time — often temporary. |
Fix connections, or continue anyway
Fix Connections takes you to reconnect the channel that failed. That is almost always the right answer.
Continue Anyway publishes regardless. It is there for the case where the platform is simply being slow to answer, and for when you are publishing to four channels and only one is broken — the other three still go out.
Scheduled posts are not tested in advance
The check happens when you publish, not for every scheduled post days ahead. A connection that expires between scheduling and sending fails at send time — which is why the connection status report is worth a look before a big campaign.