Why invitations spread across the day

Your daily invitation budget is spread across the day instead of going out all at once. Sending a full day of invitations in a few minutes is one of the clearest automation signals LinkedIn looks for, so Crispy paces them.

How the hourly allowance works

Your invitation cap is spread over 8 hours. With the default cap of 15 invitations per day, that is 2 per hour. If your daily cap is higher, your hourly allowance rises with it: an account set to 35 per day gets 5 per hour. Accounts on a very low cap, such as the first days of warm-up, always get at least 1 per hour.

It is a rolling hour, not a clock hour. Crispy counts the invitations sent in the last 60 minutes, so a slot opens as the oldest one ages out. You do not wait for the top of the hour.

What happens when you reach it

The invitation is declined and the response tells you how many minutes until the next slot opens. Nothing is lost and nothing is queued, so send it again once a slot frees up.

This is not the same as reaching your daily cap. A daily cap means you are finished with that category until the counters reset at midnight UTC. The hourly allowance is a short wait, usually well under an hour.

What it applies to

Invitations you send directly, through an AI client, the CLI, or the API. Campaigns already spread their sends across the day, so they are unaffected. Both draw on the same daily budget, so a busy campaign day leaves fewer slots for manual invitations.

Use get_account to see your invitation cap and today's usage.

If you have a genuine reason to send a batch quickly, raise the daily cap with manage_outreach_settings using action 'limits'. The hourly allowance scales with it. Raising the cap raises the risk too, so treat it as a deliberate decision rather than a default.