-
Notifications
You must be signed in to change notification settings - Fork 31
LinkedIn ‧ Terms of Service ‧ not tracked anymore #4091
Copy link
Copy link
Open
Labels
access limit exceededFetching failed with a 429 (too many requests) HTTP code - Auto-managed by OTA engineFetching failed with a 429 (too many requests) HTTP code - Auto-managed by OTA engine
Description
No version of the Terms of Service of service LinkedIn is recorded anymore since 2 April 2026 at 0:43:43 UTC
The source document has been recorded as a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.
What went wrong
- Fetch failed: Received HTTP code 429 when trying to fetch 'https://www.linkedin.com/legal/l/service-terms'
How to resume tracking
First of all, check if the source documents are accessible through a web browser:
If the source documents are accessible through a web browser
- Try updating the selectors.
- Try switching client scripts on with expert mode.
If the source documents are not accessible anymore
- If the source documents have moved, find their new location and update it.
- If these terms have been removed, move them from the declaration to its history file, using
2026-04-02T00:43:43Zas thevalidUntilvalue. - If the service has closed, move the entire contents of the declaration to its history file, using
2026-04-02T00:43:43Zas thevalidUntilvalue.
If none of the above works
If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.
References
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
access limit exceededFetching failed with a 429 (too many requests) HTTP code - Auto-managed by OTA engineFetching failed with a 429 (too many requests) HTTP code - Auto-managed by OTA engine