Common Error Messages

This article covers the most frequently encountered error messages in AcaTrove, what causes them, and how to resolve them.

"An unexpected error occurred"

This is a general error that appears when an operation fails without a more specific message. It can occur on project pages, lab views, or task lists.

Steps to resolve:

1. Refresh the page and try the action again.
2. Check your internet connection. AcaTrove requires a stable connection to communicate with the server.
3. If the error persists, clear your browser cache and reload.
4. Contact support if the problem continues after these steps, and include the page URL where the error occurred.

"Unauthorized" or "Please log in again to continue"

Your session has expired or your authentication token is no longer valid. AcaTrove displays a session-expired dialog prompting you to sign in again.

Steps to resolve:

1. Sign in through the dialog that appears. Your unsaved work on the current page may be preserved.
2. If the dialog does not appear, navigate to the login page manually at /auth/login.
3. See Login and Authentication Issues for more detailed guidance.

"Failed to upload file"

The file upload did not complete successfully. This can happen due to network interruptions, unsupported file formats, or exceeding size limits.

Steps to resolve:

1. Check that your file type is supported. Publications accept PDF, DOC, DOCX, TXT, MD, RTF, PPT, PPTX, XLS, and XLSX files.
2. Verify your file is within the size limit (up to 100 MB for publications, 10 MB for CVs).
3. Try uploading over a wired connection if you are on an unstable network.
4. See Upload and File Issues for format-specific guidance.

"Failed to load documents" or "Failed to load projects"

The application could not retrieve data from the server. This typically indicates a temporary connectivity issue between the frontend and backend services.

Steps to resolve:

1. Wait a few seconds and refresh the page.
2. Check whether other pages in AcaTrove load correctly. If they do, the issue may be specific to one data source.
3. If you are an administrator, verify that backend services are running by checking the API Health dashboard at /admin/api-health.

"Invite failed" or "Could not send invitation"

An error occurred while inviting a collaborator to a project or lab.

Steps to resolve:

1. Confirm the email address is valid and correctly formatted.
2. Check whether you have reached the collaborator limit for your subscription tier.
3. If you see "COLLABORATOR_LIMIT_REACHED," you will need to upgrade your plan or remove an existing collaborator before adding a new one.

"Failed to test connection"

This error appears in the admin integrations panel when a connector cannot reach the external service.

Steps to resolve:

1. Verify the credentials and endpoint URL you provided are correct.
2. Check that the external service is online and accessible from your network.
3. Review any firewall or proxy settings that may block outbound connections.

"Something went wrong with the AI chat"

The AI service did not return a response. See AI Features Not Working for detailed troubleshooting steps.

Tips

• Most transient errors resolve after a page refresh. Try this first before investigating further.
• When reporting an issue to support, include the exact error message, the page URL, and the action you were performing. This information significantly speeds up diagnosis.
• Browser developer tools (F12 on most browsers) can reveal additional error details in the Console tab, which are helpful when working with support.