Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sony.comTerms of Service ‧ not tracked anymore #1184

Open
1 task
OTA-Bot opened this issue Oct 27, 2023 · 10 comments
Open
1 task

sony.comTerms of Service ‧ not tracked anymore #1184

OTA-Bot opened this issue Oct 27, 2023 · 10 comments
Labels
403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA]

Comments

@OTA-Bot
Copy link
Collaborator

OTA-Bot commented Oct 27, 2023

No version of the Terms of Service of service sony.com is recorded anymore since 27 October 2023 at 1:34:31 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

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

Edit the declaration:

  • 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 2023-10-27T01:34:31Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2023-10-27T01:34:31Z as the validUntil value.

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

@OTA-Bot OTA-Bot added the timeout Fetching fails with a timeout error [managed by OTA] label Oct 27, 2023
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Oct 27, 2023

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

@OTA-Bot OTA-Bot closed this as completed Oct 27, 2023
@OTA-Bot OTA-Bot added 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] and removed timeout Fetching fails with a timeout error [managed by OTA] labels Nov 28, 2023
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Nov 28, 2023

No version of the Terms of Service of service sony.com is recorded anymore since 28 November 2023 at 19:46:24 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

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

Edit the declaration:

  • 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 2023-11-28T19:46:24Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2023-11-28T19:46:24Z as the validUntil value.

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

@OTA-Bot OTA-Bot added to clarify Default failure label [managed by OTA] and removed 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] labels Jan 10, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Jan 10, 2024

No version of the Terms of Service of service sony.com is recorded anymore since 10 January 2024 at 18:41:32 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

  • Navigation timeout of 30000 ms exceeded

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

Edit the declaration:

  • 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 2024-01-10T18:41:32Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-01-10T18:41:32Z as the validUntil value.

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

@OTA-Bot OTA-Bot reopened this Mar 28, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented May 31, 2024

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

@OTA-Bot OTA-Bot closed this as completed May 31, 2024
@OTA-Bot OTA-Bot reopened this May 31, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Jul 14, 2024

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

@OTA-Bot OTA-Bot closed this as completed Jul 14, 2024
@OTA-Bot OTA-Bot reopened this Jul 14, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Jul 31, 2024

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

@OTA-Bot OTA-Bot closed this as completed Jul 31, 2024
@OTA-Bot OTA-Bot reopened this Aug 1, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Aug 3, 2024

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Aug 6, 2024

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

@OTA-Bot OTA-Bot closed this as completed Aug 6, 2024
@OTA-Bot OTA-Bot reopened this Aug 7, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Aug 7, 2024

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

@OTA-Bot OTA-Bot closed this as completed Aug 7, 2024
@OTA-Bot OTA-Bot reopened this Aug 8, 2024
@OTA-Bot OTA-Bot removed the to clarify Default failure label [managed by OTA] label Oct 29, 2024
@OTA-Bot OTA-Bot added the 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] label Oct 29, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Oct 29, 2024

No version of the Terms of Service of service sony.com is recorded anymore since 29 October 2024 at 18:13:47 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

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

Edit the declaration:

  • 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 2024-10-29T18:13:47Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-10-29T18:13:47Z as the validUntil value.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA]
Projects
None yet
Development

No branches or pull requests

1 participant