NexaLink Troubleshooting#

License activation or plan features are unavailable#

Confirm that the License Key belongs to NexaLink, the license is active, the domain is correct, and the activation limit has not been reached. Refresh the license status after an administrator changes the plan. Local settings cannot grant Premium features.

The API rejects a request or returns HTTP 422#

Update NexaLink to the latest version and retry the analysis. HTTP 422 usually means the payload does not satisfy the API contract, such as a candidate or taxonomy list exceeding its limit. If it continues, record the request ID and sanitized validation message without sharing tokens, API keys, or sensitive article content.

HTTP 502 or the provider cannot produce valid suggestions#

Common causes include a temporary provider outage, invalid model output, unsupported model, rate limit, insufficient BYOK balance, or connection timeout. Retry with a new request, check the selected provider and model, and use Default AI to distinguish a BYOK issue from a website connectivity problem.

Analysis returns 0 recommendations#

Zero results may mean there is no sufficiently relevant target, confidence is too strict, the anchor matches an excluded term, the destination is already linked, or link rules are too restrictive. Add relevant Published content or relax the policy gradually.

Apply is rejected#

An anchor missing, ambiguous, or excluded HTML context message means NexaLink cannot safely insert the link. The anchor may appear multiple times or already be inside a link, heading, code block, or excluded element. Choose another recommendation or add the link manually after reviewing the context.

If the same anchor is offered for several destinations, applying one link can invalidate the other recommendations. Reanalyze the post after content changes.

The queue is not moving#

Open NexaLink > Analysis and review the status and last error. Confirm that WP-Cron is enabled and loopback requests are not blocked. Low-traffic websites should use a server cron that calls:

https://your-domain.example/wp-cron.php

Find sources shows 0 queued#

This usually means the same campaign source-target pairs are already queued or analyzed. Click View queue on the campaign card and review Finished/Failed, then open Opportunities. Do not create duplicate campaigns only to force the same jobs to run.

Information for support#

Include the WordPress, PHP, and NexaLink versions; AI Engine; page and action; post/campaign ID; time and timezone; HTTP status; request ID; queue status; and a sanitized error message.

Never send a complete License Key, bearer token, provider API key, private key, HMAC secret, database credentials, or wp-config.php.