Linkedin Profile Full Sections Scraper + EMAIL | No Cookies
Pricing
$10.00 / 1,000 results
Linkedin Profile Full Sections Scraper + EMAIL | No Cookies
Scrape complete LinkedIn profile data including work experience, education history, certifications, and location details. Get structured information from any public LinkedIn profile using their username.
5.0 (4)
Pricing
$10.00 / 1,000 results
16
Total users
208
Monthly users
124
Runs succeeded
>99%
Issues response
1.5 hours
Last modified
9 days ago
Distinguish 404 Errors from Other Failures in Actor Output
Open
When processing LinkedIn profile URLs, the actor currently returns a generic error for both inaccessible pages and legitimate 404 (Page Not Found) responses. This makes it difficult to programmatically differentiate between temporary access issues and permanently unavailable profiles.
Observed Behavior:
Case 1: Accessible but Failing Profile:
URL: https://www.linkedin.com/in/rolando-p%C3%A9rez-rebollo-8b0808b9
Expected: Actor should successfully retrieve data.
Actual: Actor returns an error. (Further investigation needed to determine the root cause for this specific URL.)
Case 2: 404 Not Found Profile:
URL: https://www.linkedin.com/in/carlosnavarrofernandez
Expected: Actor should return a specific 404 error code or indicator.
Actual: Actor returns a generic error, even though the URL redirects to a standard LinkedIn 404 page when accessed manually.
Problem:
The inability to distinguish between different types of errors prevents us from implementing efficient retry logic and data management. Specifically, for 404 errors, we want to avoid future attempts to retrieve data for profiles that are permanently unavailable.
Proposed Solution (Feature Request):
Please implement a mechanism within the actor's error output to clearly differentiate 404 "Page Not Found" errors from other types of failures. This could be achieved by:
Including a specific error code (e.g., statusCode: 404) in the error object.
Adding a distinct error message (e.g., errorMessage: "Profile Not Found (404)").
Providing an errorType field (e.g., errorType: "NOT_FOUND").
