User-Facing Error Messages

This document lists all error messages that users may encounter when using the application. All error messages are sanitized to ensure sensitive information (file paths, stack traces, internal details) is never exposed to users.

Note for Developers: Full error details with stack traces are always logged server-side for debugging purposes. Users only see the sanitized messages listed below.

Backend Error Messages

These messages are generated by the backend error handler (backend/routes/error_handlers.py) and returned in API responses.

1. The run ID you provided is not valid. Please check and try again.

When it occurs: Invalid or malformed run ID provided in requests.

Tests:

test_error_handlers.py::test_invalid_id_exception
test_pipeline_runner_errors.py::test_invalid_run_id_empty_string
test_pipeline_runner_errors.py::test_invalid_run_id_malformed
test_pipeline_routes.py::test_get_run_files_invalid_run_id_sanitized
test_merfish_route.py::test_merfish_route_invalid_run_id
test_merfish_route.py::test_merfish_route_propagates_pipeline_runner_errors
test_seqfish_route.py::test_seqfish_route_invalid_run_id
test_seqfish_route.py::test_seqfish_route_propagates_pipeline_runner_errors
test_oligoseq_route.py::test_oligoseq_route_invalid_run_id
test_oligoseq_route.py::test_oligoseq_route_propagates_pipeline_runner_errors
test_scrinshot_route.py::test_scrinshot_route_invalid_run_id
test_scrinshot_route.py::test_scrinshot_route_propagates_pipeline_runner_errors

2. Your session has expired. Please refresh the page and try again.

When it occurs: Anonymous user session ID is missing or invalid.

Tests:

test_error_handlers.py::test_value_error_session
test_pipeline_runner_errors.py::test_missing_session_id

3. Unable to access your data directory. Please try again or contact support.

When it occurs: User data directory doesn’t exist or cannot be accessed.

Tests:

test_error_handlers.py::test_value_error_directory
test_error_handlers.py::test_runtime_error_directory
test_pipeline_runner_errors.py::test_missing_user_directory

4. The information you provided is not valid. Please check your input and try again.

When it occurs: Invalid form data or missing required fields.

Tests:

test_error_handlers.py::test_value_error_generic
test_genomic_routes.py::test_genomic_cascaded_ncbi_invalid_input
test_genomic_routes.py::test_genomic_cascaded_ensembl_invalid_input
test_genomic_routes.py::test_genomic_cascaded_custom_invalid_input

5. The pipeline failed to execute. Please check your input and try again.

When it occurs: Pipeline subprocess execution fails.

Tests:

test_error_handlers.py::test_runtime_error_pipeline
test_pipeline_runner_errors.py::test_subprocess_failure
test_genomic_routes.py::test_genomic_cascaded_ncbi_subprocess_failure
test_genomic_routes.py::test_genomic_cascaded_ensembl_subprocess_failure
test_genomic_routes.py::test_genomic_cascaded_custom_subprocess_failure

6. An error occurred while running the pipeline. Please try again.

When it occurs: Generic runtime error during pipeline execution.

Tests:

test_error_handlers.py::test_runtime_error_generic

7. A required file is missing. Please check your input files and try again.

When it occurs: Required file doesn’t exist or cannot be found.

Tests:

test_error_handlers.py::test_file_not_found_error
test_pipeline_routes.py::test_get_run_file_not_found_sanitized

8. Something went wrong while accessing files. Please try again or contact support if the problem persists.

When it occurs: File permission errors (internal server issue).

Tests:

test_error_handlers.py::test_permission_error
test_pipeline_routes.py::test_get_run_file_permission_error_sanitized
test_pipeline_runner_errors.py::test_temp_file_creation_error

9. Some required information is missing. Please check your input and try again.

When it occurs: Missing required configuration parameter.

Tests:

test_error_handlers.py::test_key_error

10. Something went wrong. Please try again or contact support if the problem persists.

When it occurs: Generic server errors or errors containing sensitive patterns.

Tests:

test_error_handlers.py::test_generic_exception
test_error_handlers.py::test_sensitive_patterns_sanitized
test_error_handlers.py::test_long_error_message_truncated
test_pipeline_runner_errors.py::test_config_generation_error
test_pipeline_runner_errors.py::test_catch_all_exception_handler

11. The run you’re looking for doesn’t exist or you don’t have permission to access it.

When it occurs: Run doesn’t exist in database or user doesn’t have access.

Tests:

test_pipeline_routes.py::test_get_pipeline_run_error_message_display (indirectly)

12. Unauthorized

When it occurs: User doesn’t have permission to access the resource.

Tests: (Covered by route logic, not explicitly tested)

13. We couldn’t process your genomic data. Please check your input and try again.

When it occurs: Error in genomic route processing (wrapper message).

Tests:

test_genomic_routes.py::test_genomic_cascaded_ncbi_invalid_input
test_genomic_routes.py::test_genomic_cascaded_ncbi_subprocess_failure
test_genomic_routes.py::test_genomic_cascaded_ensembl_invalid_input
test_genomic_routes.py::test_genomic_cascaded_ensembl_subprocess_failure
test_genomic_routes.py::test_genomic_cascaded_custom_invalid_input
test_genomic_routes.py::test_genomic_cascaded_custom_subprocess_failure
test_genomic_routes.py::test_genomic_routes_no_str_e_exposed

Frontend Fallback Messages

These messages are generated by the frontend error handler (src/components/errorHandler.ts) when the backend doesn’t provide a specific error message.