Troubleshooting

This page lists common Zluri issue codes you may encounter related to dataset, widget creation, or editing, along with recommended resolutions.

Issue 1000: Datasource Too Large to Query

Your dataset may contain too much data for the current query to process efficiently, causing timeouts.

Resolution:
Filter or reduce the dataset size by querying a smaller subset.

Issue 1001: Database Under Unusual Load

The backend database is under high load, causing delays.

Resolution:
Simplify the query or retry during off-peak hours.

Issue 1002: Unexpected Database Error

An internal database error occurred during query execution.

Resolution:
Check database logs or consult your database admin.

Issue 1003: Syntax Error in Query

Your query contains typos or invalid syntax.

Resolution:
Double-check all field names, table references, and SQL structure.

Issue 1004: Column Deleted or Renamed

The query refers to a column that no longer exists.

Resolution:
Update your query to use existing column names.

Issue 1005: Table Deleted or Renamed

The referenced table has been removed or renamed.

Resolution:
Verify table names and update the query.

Issue 1006: Missing Query Parameters

Required query parameters were omitted or are malformed.

Resolution:
Ensure all required parameters are defined and formatted in valid JSON.

Issue 1007: Invalid Hostname for Database Connection

The hostname used cannot be resolved.

Resolution:
Check for typos and verify network settings.

Issue 1008: Database Port Closed

The database port is blocked or inactive.

Resolution:
Check firewall settings and confirm correct port usage.

Issue 1009: Host Unreachable

The target host is offline or not accessible.

Resolution:
Validate network access and firewall rules.

Issue 1010–1011: Unexpected Zluri Backend Error

An internal error occurred during query execution.

Resolution:
Contact Zluri Admin or Support.

Issue 1012–1014: Invalid Username or Password

Authentication failed due to incorrect credentials.

Resolution:
Check the database username and password.

Issue 1015–1016: Database or Schema Not Found

The database or schema does not exist or was renamed.

Resolution:
Confirm the name and user access permissions.

Issue 1017: Insufficient Permissions to Connect

The user lacks required database roles.

Resolution:
Ensure the account has Viewer and Job User roles or equivalent.

Issue 1018–1019: Missing or Malformed Configuration Parameters

Essential configuration details are absent or invalid.

Resolution:
Review and correct JSON formatting of all parameters.

Issue 1020: Incorrect Request Payload Schema

The request data does not match the expected format.

Resolution:
Match the payload structure to the schema definition.

Issue 1021: Results Backend Not Configured for Async Queries

Zluri is not set up to handle asynchronous query results.

Resolution:
Contact your administrator to configure the results backend.

Issue 1022: Database Does Not Allow Data Manipulation

Only SELECT queries are allowed.

Resolution:
Restrict queries to read-only operations, or contact your admin.

Issue 1023–1025: CTAS/CVAS Query Issues

The query contains improper CTAS (Create Table As Select) or CVAS (Create View As Select) statements.

Resolution:
CTAS must end with a single SELECT; CVAS should have one SELECT with no trailing semicolons.

Issue 1026: Query Complexity or Timeout

Query is too complex or exceeds execution time limits.

Resolution:
Optimize the query or increase timeout settings (admin-only).

Issue 1027: Database Running Too Many Queries

Concurrent query limit reached.

Resolution:
Retry later or request system scaling from the admin.

Issue 1028: Malformed Query Parameters

Query template parameters are incorrectly formatted.

Resolution:
Use double braces syntax, e.g., {{ ds }}.

Issue 1029–1030: Nonexistent Database Objects or Syntax Errors

Invalid schema/table/column names or broken syntax.

Resolution:
Correct the object references and syntax.

Issue 1031–1033: Results Backend Data Missing or Corrupted

Query result is unavailable, deleted, or invalid.

Resolution:
Re-run the query to regenerate results.

Issue 1034: Invalid Database Port Number

Port is outside the valid range (0–65535).

Resolution:
Use a valid port number.

Issue 1035: Failed Async Query Start on Worker

Zluri failed to launch a remote async query worker.

Resolution:
Admin intervention required.

Issue 1036: Database Deleted

The referenced database has been removed.

Resolution:
Update your connection settings or consult your admin.

If your issue isn’t mentioned here, feel free to submit a ticket or contact us directly at [email protected].