Who this is for: Recruiters on the AIRA Plan whose Social Connection Request or Social Message steps are not sending.

Start here

Social step failures fall into one of four categories: the account isn't connected, the connection has expired, the step is hitting a daily limit, or the recipient's data is missing. Work through the checks below in order — most issues resolve at step one or two.

Check 1: Is your Social account connected?

Go to Settings → Integrations.

If it shows Connected: move to Check 2
If it shows Disconnected or Not Connected: click Connect and complete the OAuth flow. Once reconnected, go to the sequence Errors tab and Retry the affected recipients.

Important: Every recruiter who sends Social steps needs to connect their own Social account individually. If you're an Admin troubleshooting on behalf of someone else, they need to do this themselves — you can't connect Social account on their behalf.

Check 2: Has the Social account connection expired?

Social connections time out periodically — typically every 60 days or after a Social account password change. The integration page may still show "Connected" but the underlying session may be invalid.

If recipients are erroring on Social steps even though the integration shows Connected:

Go to Account Settings → Integrations
Click Disconnect
Click Connect and complete the OAuth flow again — log in fresh and re-authorise all requested permissions
Go to the sequence Errors tab and Retry affected recipients

Check 3: Have you authorised all required Social permissions?

During the Social OAuth flow, the platform presents a permissions screen. If you declined any permissions or clicked through too quickly, Recruiterflow won't have the access it needs to send messages or connection requests.

Symptoms: Social accounts shows Connected but steps immediately error with "Social message could not be sent because your account does not have permission."

Fix: Disconnect and reconnect the Social account, making sure to Allow all permissions on the Account authorisation screen — do not uncheck any boxes.

Check 4: Is the recipient's Social URL missing from their profile?

Recruiterflow needs the recipient's Social profile URL to send a connection request or Social message. If the URL is missing, the step errors immediately.

How to check: Open the recipient's profile in Recruiterflow and look for the Social URL field. If it's blank, add it.

After adding: Go to the sequence Errors tab and Retry the recipient.

If you're seeing this across many recipients: Your recipient list likely has a high proportion of profiles without Social URLs. Consider filtering your recipient list to only include profiles with a Social URL before adding them to sequences with Social steps.

Check 5: Is the daily Social limit reached?

If steps are not erroring but also not sending, the most likely cause is that your sender's daily Social cap has been reached. In this case the steps aren't failing — they're queued.

How to check: Look at the Daily Channel Usage Summary on the Sequences page. If the Social Messages or Social Connection Requests card shows an alert state (amber/red border) or the count equals your daily limit, you've hit the cap.

What happens next: Recruiterflow will automatically send the queued steps as capacity frees up over the next 24 hours. No manual action is needed unless you want to change your daily limit.

To change your Social limit: Admins can adjust per-sender Social caps in Settings → Automation Settings →Limits and Visibility Configuration. Note that the Social platform's own platform limits apply — Recruiterflow cannot exceed them regardless of what's configured.

Check 6: Is this a Social Message step where the recipient isn't connected?

Social Message steps require the recipient to already be a first-degree connection with the sender. If they're not connected, Recruiterflow cannot deliver the message and the step errors.

Error message: "Social message could not be delivered. Recipient is not a first-degree connection."

Fix options:

Add a Social Connection Request step earlier in the sequence — before the Social Message step — and give recipients time to accept before the message step fires
Use Conditional Branching to route unconnected recipients to an email step instead (AIRA Plan required)
Skip Step for the affected recipients and continue with the remaining steps

Check 7: Is this an AIRA Plan feature on a non-AIRA Plan account?

Social Connection Request and Social Message steps require an AIRA Plan. If your account has been downgraded or you're testing on a non-AIRA Plan workspace:

Social step cards in the builder appear greyed out with an upgrade lock icon
Any recipients on Social steps will be blocked and cannot be retried until the plan is restored

Fix: Contact your Recruiterflow account manager to verify your plan status.