Isenção de responsabilidade: Este artigo foi gerado usando tradução automática.

Troubleshooting analytics issues

Prev Next
This content is currently unavailable in Portuguese. You are viewing the default (English) version.

Document360 enforces a 5-second validation timeout for link verification. If a request exceeds this limit, the system may flag the link as Unknown or Broken. Even if the link is functional, it may be incorrectly marked as broken due to the timeout restriction.

Steps to resolve:

  1. Manually check the URL

    1. Open the link in a browser to confirm if it loads correctly.

    2. If the page loads, the link may have been incorrectly flagged as broken.

  2. Validate the link using Postman

    1. Open Postman and create a new request tab.

    2. Enter the URL and select the GET method.

    3. Click Send to check the response status.

  3. Interpret the HTTP response status

    1. If the response is 200 OK, the link is functional.

    2. If the response code is anything other than 200, the link might be broken.

Postman interface showing a GET request with highlighted parameters and response status.

Some of the important status codes are:

Status code

Status description

Description

200 OK

Success

The request was successful, and the expected response was returned.

201 Created

Resource created

The request was successful, and a new resource was created.

204 No content

No response body

The request was successful, but there is no response body (common for DELETE requests).

400 Bad request

Invalid request

The request has incorrect syntax or missing parameters.

401 Unauthorized

Authentication required

The request lacks valid authentication credentials (e.g., missing or incorrect API key).

403 Forbidden

Access denied

The request is valid, but the user does not have permission to access the resource.

404 Not found

Resource missing

The requested resource does not exist, or the endpoint is incorrect.

405 Method not allowed

Invalid method

The HTTP method (GET, POST, etc.) is not allowed for this endpoint.

500 Internal server error

Server issue

A generic error indicating something went wrong on the server.

502 Bad gateway

Invalid response

The server received an invalid response from an upstream server.

503 Service unavailable

Server overloaded

The server is down or overloaded with requests.

504 Gateway timeout

Timeout error

The server did not receive a response from another service in time.


Bot-blocking and security restrictions

Some external websites use bot-detection or security measures that actively block automated validation requests. When Document360’s link validator attempts to reach these URLs, the site refuses the request, and the link is flagged as Broken or Unknown — even though it opens normally in a browser for your readers.

Common examples include:

  • Sites with strict bot-detection (such as Cloudflare-protected pages).

  • Login-protected pages, intranet sites, or SSO-protected resources that cannot authenticate an automated request.

  • Platforms that return a different response to automated tools than to browsers (for example, returning a 403 Forbidden code to bots while loading correctly for human visitors).

Steps to resolve:

  1. Open the link in an incognito or private browser window to confirm it loads correctly for a reader.

  2. If the page loads, the link is functional. The broken status is caused by the external site refusing the validator’s automated request, not by a problem with the link itself.

  3. In Link Analytics, add the link to the Ignore list to exclude it from future validation reports. Navigate to Manage links, select the link, and click Ignore.

If you are unsure whether a link is genuinely broken or only flagged due to bot-blocking, check the HTTP response using Postman as described above. A 403 Forbidden response from a URL that loads correctly in a browser is a strong indicator of bot-blocking rather than a genuinely broken link.

Se o problema persistir após seguir essas etapas, entre em contato com a equipe de suporte do Document360 para obter mais assistência: Entre em contato com o suporte do Document360


FAQ

The recycle bin icon indicates that the articles containing those links have been deleted and moved to the recycle bin, but have not been permanently deleted. Since the articles can still be restored, the associated links continue to be included in the scheduled link validation process.

Once the articles are permanently deleted from the recycle bin, those links will no longer be validated or displayed in Link Analytics.

This behavior occurs when an image is embedded directly into the article as base64-encoded data instead of being hosted at an external URL.

The Link Validator checks whether a web address points to a valid and accessible resource. Since base64-encoded images are embedded inline within the article and do not have a separate URL, there is no web address available for validation. As a result, the validator may incorrectly flag the image as a broken link, even though the image continues to display correctly in the browser.

To avoid this behavior, it is recommended to host images at a publicly accessible URL (for example, using cloud storage or an external image hosting service) and insert them into the article using the image URL instead of embedding them as base64-encoded data.