Invitation failed to send

Invitations can fail for several reasons. Crispy checks the obvious ones before sending, so most failures come back as a clear message instead of a wasted attempt.

• Already pending: you get 'Invitation already pending' with the date it was sent. The earlier invitation is still waiting for a response; no action needed.
• Already connected: sending an invitation to an existing connection has no effect, so Crispy refuses it and suggests 'send_message' instead.
• Blocked: the person is on your block list, so the send is refused with reason 'blacklisted'.
• Daily invitation limit reached: invitations are capped per day to protect the account (default 15). Check 'get_account' for remaining capacity; the counter resets at midnight UTC.
• Recently withdrawn or re-invited too soon: LinkedIn enforces a resend cooldown of roughly three weeks. When a send returns 'Cannot resend yet', campaigns automatically park that contact for 21 days before reconsidering them.
• The person cannot be invited: their profile restricts incoming invitations or is deactivated. Campaigns mark these as permanently skipped rather than retrying forever.

Read the specific reason in the error before retrying. Retrying an 'already pending' or cooldown failure burns budget without changing the outcome.

One formatting note: the personalized note on an invitation is capped at 300 characters, and shorter personalized notes tend to get better acceptance.