Error Messages in Tabidoo

1. Client-side Errors (4xx)

Errors in this group indicate a problem with the request sent by the client (browser, script, or integration).

400 – Bad Request

Meaning: The request was malformed or missing required data.
 Typical causes:

• Missing required field in API request
• Invalid JSON body
• Using unsupported parameter values

What to do:

• Check the API documentation for required fields
• Validate the JSON syntax
• Ensure field values match the expected type or format

401 – Unauthorized

Meaning: Authentication failed.
 Typical causes:

• Invalid or expired API token
• User not logged in

 What to do:

• Check your API token
• Generate a new token if necessary
• Log in again and verify permissions

403 – Forbidden

Meaning: You are authenticated but not allowed to access the resource.
 Typical causes:

• Insufficient user rights for the table, workflow, or dataset
• Trying to use an endpoint not available in your pricing plan

What to do:

• Verify your role and permissions
• Contact the application owner if needed
   

404 – Not Found

Meaning: The requested resource doesn’t exist.
 Typical causes:

• Wrong endpoint URL
• Invalid record ID
• Deleted object

What to do:

• Double-check the URL or record identifier
• Confirm that the resource still exists

429 – Too Many Requests

Meaning: You have reached your API limit (rate limiting).
 What to do:

• Wait before retrying
• Monitor your API usage with getCurrentUserTechnicalLimits()
• Consider upgrading your plan if you regularly hit the limit
   

2. Server-side Errors (5xx)

These errors indicate a problem on the Tabidoo side. They are less common but may occur.

500 – Internal Server Error

Meaning: Something unexpected happened on the server.

What to do:

• Retry the request after a short delay
• If the issue persists, contact Tabidoo support

502 – Bad Gateway

Meaning: Temporary communication error between services.

What to do:

• Retry the operation
• The issue usually resolves itself quickly
   

503 – Service Unavailable

Meaning: The server is temporarily overloaded or under maintenance.

What to do:

• Wait and try again later
• Check the Tabidoo status page (in the future)

504 – Gateway Timeout

Meaning: The server took too long to respond.

What to do:

• Retry the request
• Optimize queries or workflows if they take too long

3. Application-level Errors

Besides standard HTTP codes, Tabidoo may also return errors specific to application logic.

Examples include:

• Validation errors (e.g., wrong data type in a field)
• Workflow execution errors (e.g., failed condition, missing related record)
• Storage limits exceeded (e.g., too many records, too large attachments)

What to do:

• Carefully read the error description
• Fix the input data or workflow configuration
• Check your plan limits

4. Best Practices for Handling Errors

To ensure stability and better user experience, follow these practices:

• Log all errors – especially in automated integrations (System log extension)
• Use retries with backoff – for temporary errors (500, 502, 503) - contact us: support@tabidoo.cloud
• Set up monitoring and alerts – to detect when limits are close to being reached - via function getCurrentUserTechnicalLimits()
  
   

Contact support – if you cannot resolve the issue on your own (support@tabidoo.cloud)