Testing connections before you publish

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.

CONTINUING PAST A REAL FAILURE PUBLISHES NOTHING ON THAT CHANNEL

If the connection has genuinely expired, continuing does not fix it — the post simply fails there and you find out afterwards. Reconnect first unless you are confident it was a timeout.

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.