Why do requests continue to be sent after the campaign is stopped?

In Scout, when you send a connection request on LinkedIn, our system records the date when the request was initiated. However, LinkedIn itself does not show the date the request was sent. Instead, it only displays the date the request was accepted. This can lead to confusion when you stop or delete a campaign, but requests continue to be accepted later.

Here’s How It Works:

1. Sending a Connection Request:
   Let’s say you have an active campaign, and a connection request is sent to a LinkedIn user on October 10th.

2. Campaign Stops:
   On October 12th, you decide to stop or delete the campaign, which should effectively end the connection request process for new contacts.

3. Acceptance Date:
   The recipient of your connection request accepts it on October 31st.

4. Date Displayed:
   When you view this connection on LinkedIn, you’ll see that the connection request from your stopped campaign was accepted on October 31st, but LinkedIn won’t show when the invite was originally sent on October 10th.

Why Does This Happen?

The delay between when the campaign stops and when the connection request is accepted is due to how LinkedIn handles connection request data. The date shown is based on the acceptance of the request, not when it was initially sent. This is why it might appear as though the request was sent on the same day it was accepted, even though the request was made earlier.