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

AlexaTerms of Service ‧ not tracked anymore #1018

Open
1 task
OTA-Bot opened this issue Oct 18, 2023 · 19 comments
Open
1 task

AlexaTerms of Service ‧ not tracked anymore #1018

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

Comments

@OTA-Bot
Copy link
Collaborator

OTA-Bot commented Oct 18, 2023

No version of the Terms of Service of service Alexa is recorded anymore since 18 October 2023 at 14:45:22 UTC

The source document has not been recorded in a snapshot, thus no version can be extracted.

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-18T14:45:22Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2023-10-18T14:45:22Z 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 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] label Oct 18, 2023
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Oct 28, 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 28, 2023
@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 Dec 5, 2023
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Dec 5, 2023

No version of the Terms of Service of service Alexa is recorded anymore since 5 December 2023 at 8:37:58 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 2023-12-05T08:37:58Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2023-12-05T08:37:58Z 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 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] and removed to clarify Default failure label [managed by OTA] labels Dec 7, 2023
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Dec 7, 2023

No version of the Terms of Service of service Alexa is recorded anymore since 7 December 2023 at 11:51:43 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-12-07T11:51:43Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2023-12-07T11:51:43Z 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 selectors Extraction selectors are outdated [managed by OTA] and removed 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] labels Jan 24, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Jan 24, 2024

No version of the Terms of Service of service Alexa is recorded anymore since 24 January 2024 at 6:30:46 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-01-24T06:30:46Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-01-24T06:30:46Z 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 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] and removed selectors Extraction selectors are outdated [managed by OTA] labels Jan 24, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Jan 24, 2024

No version of the Terms of Service of service Alexa is recorded anymore since 24 January 2024 at 12:30:35 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-01-24T12:30:35Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-01-24T12:30:35Z 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 Feb 2, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Feb 2, 2024

No version of the Terms of Service of service Alexa is recorded anymore since 2 February 2024 at 0:31:02 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-02-02T00:31:02Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-02-02T00:31:02Z 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 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] and removed to clarify Default failure label [managed by OTA] labels Feb 16, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Feb 16, 2024

No version of the Terms of Service of service Alexa is recorded anymore since 16 February 2024 at 6:30: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

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-02-16T06:30:32Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-02-16T06:30: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 added selectors Extraction selectors are outdated [managed by OTA] and removed 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] labels Mar 8, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Mar 8, 2024

No version of the Terms of Service of service Alexa is recorded anymore since 8 March 2024 at 18:30:46 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-03-08T18:30:46Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-03-08T18:30:46Z 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 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] and removed selectors Extraction selectors are outdated [managed by OTA] labels Mar 9, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Mar 9, 2024

No version of the Terms of Service of service Alexa is recorded anymore since 9 March 2024 at 0:30:36 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-03-09T00:30:36Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-03-09T00:30:36Z 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 22, 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 22, 2024
@OTA-Bot OTA-Bot reopened this May 23, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented May 25, 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 25, 2024
@OTA-Bot OTA-Bot reopened this May 25, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented May 26, 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 26, 2024
@OTA-Bot OTA-Bot reopened this May 26, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented May 28, 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 28, 2024
@OTA-Bot OTA-Bot reopened this May 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 Jun 1, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Jun 1, 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 Jun 1, 2024
@OTA-Bot OTA-Bot reopened this Jun 5, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Jun 5, 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 Jun 5, 2024
@OTA-Bot OTA-Bot reopened this Jun 5, 2024
@OTA-Bot OTA-Bot added selectors Extraction selectors are outdated [managed by OTA] and removed 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] labels Jun 7, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Jun 7, 2024

No version of the Terms of Service of service Alexa is recorded anymore since 7 June 2024 at 6:30:49 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-06-07T06:30:49Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-06-07T06:30:49Z 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 removed the selectors Extraction selectors are outdated [managed by OTA] label Jun 7, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Jun 7, 2024

No version of the Terms of Service of service Alexa is recorded anymore since 7 June 2024 at 12:30:40 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-06-07T12:30:40Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-06-07T12:30:40Z 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 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] label Jun 7, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Jun 8, 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 Jun 8, 2024
@OTA-Bot OTA-Bot reopened this Jun 8, 2024
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