Action Errors
Click to expand

Timeout Error

If your API / DB Query times out, it could be due to one of the following reasons
  • Your API / Database is behind a VPC which is not accessible from the appsmith Instance. This can be fixed by
    whitelisting the appsmith instance in your database or VPC.
  • Your API / Query is taking too long to respond. This can be fixed by fetching smaller datasets using
server-side pagination or increasing the timeout of the API / Query in the settings section.

Configuration Error

1
getUsers failed to execute. Please check it's configuration
Copied!
This message indicates an error in the configuration of the action. You can navigate to the API / Query in this state and see the error it encountered. If the error occurred intermittently, it is likely due to a value in the configuration not being available at the time that the API / Query was run.

Mandatory Parameter Empty Error

1
Mandatory parameters 'Action' and 'Bucket Name' are missing
Copied!
1
Required parameter 'File Path' is missing
Copied!
1
Missing action name (like `ListTables`, `GetItem` etc.)
Copied!
1
Document/Collection path cannot be empty
Copied!
1
Missing Firestore method
Copied!
A message of this type means that at least one of the mandatory / required fields in the query editor form is missing.
This error can be fixed by editing the query editor form and providing the parameter mentioned in the error message.

Missing Query Error

1
Missing required parameter: Query
Copied!
1
needs a non-empty body to work
Copied!
1
Body is null or empty
Copied!
Any one of these messages indicated that the body of the query has been left empty.
This error can be fixed by editing the query form and providing a query body.

Invalid Query Error

1
Not a valid Redis command
Copied!
1
Query preparation failed while inserting value
Copied!
A message of this type indicates that the syntax of the query body is invalid.
This error can be fixed by providing a valid syntax in the query editor form.

Encoding Error

1
File content is not base64 encoded
Copied!
This message indicates that the query was expecting a base64 encoded value as content body, but the actual value passed to it was not base64 encoded.
This error can be fixed by passing a base64 encoded value as file content parameter in the query.

Invalid Number Error

1
Parameter 'Expiry Duration of Signed URL' is NOT a number
Copied!
This message indicates that the query parameter mentioned in the message expects a number but a non-numerical value has been provided in the query form.
This error can be fixed by editing the query form and providing a valid number as input for the mentioned parameter.

JSON Parsing Error

1
Error parsing the JSON body
Copied!
1
Error converting array to ND-JSON
Copied!
1
Unable to parse condition value as a JSON list
Copied!
This message indicates that the JSON string passed to the query as a parameter is not a valid JSON string.
This error can be fixed by editing the query form and passing a valid JSON string as a parameter.