sending-refusal-costs-an-attemptlisted

# A refusal costs one attempt, not a day When the platform refuses an invitation with a temporary limit error, pause that profile for 30 to 60 minutes and then try a different person. Treat the day as a wall only after three refusals in a row with zero invites sent that day. Count the weekly invitation cap yourself so you rarely hit the error at all. ## Why We tried both extremes on our own profiles. First extreme: a refusal moved the queue by four hours, and profiles came back to the same closed door three times a day. At one point eight of our thirteen profiles had been knocking like that for five days in a row. That is exactly the pattern automation gets restricted for. Second extreme: one attempt per day, and a strike if nothing went out. It looked safe, but it measured our own rule, not the platform. With only one attempt allowed, "nothing sent today" was guaranteed after any refusal. The sending log from the days when retries were still allowed showed the opposite picture: out of 23 profile-days with refusals, invites still went out later the same day on 18. One profile was refused at 08:00 and then sent four invites after it. The real risk is the account itself, and often it belongs to a client or a real person. ## How to apply 1. On a temporary limit refusal, pause invitations on that profile for 30 to 60 minutes. Messages and replies keep going. 2. After the pause, try a different person. Do not retry the same person right away. 3. Close a queue row that was re