Troubleshooting
A build failed, a running application errors, or a domain will not verify.
Start where the evidence is: the deployment that failed, the application's own logs, or the DNS record.
The build failed
Open the deployment and read the message with its log. The message names the cause when we can identify it — a missing dependency, a failing build command, a type error — and it tells you when it cannot.
The repository could not be read
Some failures happen before any build output appears and mention that the repository could not be found. That usually means the fix is the platform's access to the repository, not the repository itself. Reconnect the GitHub account from the organization's settings, then deploy again. If the repository is still not visible, write to support@senedx.sn.
The application runs, but a page errors
SeneDx decides an application is live from the health endpoint it exposes, so an application can be running while its own routes fail. A missing runtime variable is the usual cause — an application key, a database URL. Read the runtime logs first, then the environment variables.
A domain will not verify
The TXT record has to be live at your DNS provider and match the challenge exactly. A DNS change can take a few minutes to appear. Create or correct the record, wait for it to resolve, then press Verify again.
Did this page help you?
If something here is wrong, missing or unclear, tell us and we will fix the page.
Contact support