Web Connect: Troubleshooting

Web Connect: Troubleshooting#

I see a JSONPath error message when fetching data from Web Connect#

The No rows match the given jsonpath error message appears because the syntax of a JSON path in your datastream settings is incorrect.

To resolve this issue, check the JSON paths used in your datastream settings and correct any syntax errors.

I see an encoding error message when fetching data from Web Connect#

The Adverity cannot determine the character encoding error message appears when Adverity is not sure whether the automatically detected encoding is correct.

To resolve this issue, we recommend checking the automatically detected encoding, and changing the setting if it is incorrect. If it is correct, you do not need to take any further action.

I see a codec error message when fetching data from Web Connect#

The 'ascii'/'utf-8'/etc. codec can't decode byte 0xYY in position xxxxxx error message can appear for the following reasons:

  • The encoding for your Web Connect datastream is defined incorrectly.

  • The datastream is set to parse an incorrect file type.

  • The source file contains characters with multiple encoding types.

  • The source file contains invalid or corrupted characters.

To resolve this issue, depending on the cause, you need to correct your datastream settings, ensure that the source file only contains characters with one encoding type, and remove any invalid or corrupted characters in the source file.

I see a request method error message when fetching data from Web Connect#

The Request method 'POST'/'GET' is not supported error message appears when you are trying to use an unsupported request method.

To resolve this issue, change the request method:

  • If you are trying to use the POST request method, change it to GET.

  • If you are trying to use the GET request method, change it to POST.

My Web Connect datastream was automatically paused#

Adverity automatically pauses Web Connect datastreams that have failed identically for a consecutive number of days or attempts. This prevents continuous retries of fetches that are structurally failing (for example, due to HTTP 410 Gone or 401 Unauthorized errors) and conserves resources.

When a datastream is automatically paused, a notification is sent to the workspace owner. To resume collecting data, review the datastream configuration and resolve the underlying issue causing the failures. Then, you can manually unpause the datastream.

Contents