Skip to main content

Troubleshooting Guide: All Error Codes

Table of Contents​

Gmail​

BLT1012 - NO_RECIPIENT_FOUND​

HTTP Status: 400 Bad Request | Error: No Recipient found

Description: No valid recipient email addresses found in To, CC, or BCC fields.

Common Causes: All recipient fields empty; template variables resolve to empty/undefined: {{result.email}} has no value

Solutions:

  1. Add at least one email address to To, CC, or BCC field
  2. Fix template variables: Ensure {{result.user_email}} contains valid email
  3. Test with static email first: "[email protected]"

Example:

// ❌ Wrong: { "to": [], "cc": [], "bcc": [] }
// ✅ Correct: { "to": ["[email protected]"] }

BLT1013 - ATTACHMENT_SIZE_EXCEEDS_LIMIT​

HTTP Status: 400 Bad Request | Error: Total attachment size exceeds 25 MB limit

Description: Gmail API limits total attachment size to 25 MB. Sum of all attachments exceeds this limit.

Common Causes: Single file > 25 MB; multiple files combined exceed 25 MB; base64 encoding increases size (~33%)

Solutions:

  1. Reduce file sizes: Compress files, use lower resolution images
  2. Use cloud storage links: Share download links instead of attaching
  3. Split emails: Send multiple emails with smaller attachments

Example:

// ❌ Wrong - 35 MB total: { "attachments": ["video.mp4", "image.jpg"] }
// ✅ Correct - Under 25 MB: { "attachments": ["document.pdf"] }

BLT1104 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Gmail Activity: [error details]

Description: Catch-all error for unexpected Gmail API failures, authentication issues, or network problems.

Common Causes: Invalid/expired OAuth tokens; Gmail API rate limits exceeded; service outage or network failures

Solutions:

  1. Re-authenticate: Disconnect and reconnect Gmail integration
  2. Check API limits: Wait and retry if rate limited
  3. Verify permissions: Ensure gmail.send and gmail.modify scopes

Slack​

BLT1051 - INVALID_BLOCKS​

HTTP Status: 400 Bad Request | Error: Invalid Slack blocks detected

Description: Slack blocks object missing or invalid after evaluating dynamic content. Template variables resolved to null/undefined.

Solutions: Fix template variable path: Use {{result.blocks}} instead of {{result.missing.blocks}}; ensure previous activity returns valid blocks object; test with static blocks first

BLT1052 - OBJECT_MISSING_BLOCKS_PROPERTY​

HTTP Status: 400 Bad Request | Error: Slack blocks object is missing a 'blocks' property

Description: Using message block type but object lacks required blocks array property.

Solutions: Ensure object has blocks property with array value; use Slack Block Kit Builder; verify block type is "message" not "attachment"

BLT1053 - OBJECT_MISSING_ATTACHMENTS_PROPERTY​

HTTP Status: 400 Bad Request | Error: Slack blocks object is missing an 'attachments' property

Solutions: Ensure object has attachments property: { "attachments": [...] }; use "attachment" block type, not "message"

BLT1054 - BLOCKS_PARSING_ERROR​

HTTP Status: 400 Bad Request | Error: An issue occurred while parsing the Slack Blocks

Description: Invalid JSON syntax in blocks configuration or template interpolation created malformed JSON.

Solutions: Validate JSON syntax; use Slack Block Kit Builder; check template variable outputs are valid JSON; test with static blocks first

BLT1055 - NO_ACTIONS_SECTION_IN_BLOCKS​

HTTP Status: 400 Bad Request | Error: No actions section found in the blocks

Description: Workflow pause enabled but blocks don't contain actions section with buttons.

Solutions: Add actions block with buttons when pause workflow is enabled; use interactive elements for workflow approval; disable pause workflow if not needed

BLT1056 - NO_BUTTONS_IN_ACTION​

HTTP Status: 400 Bad Request | Error: No buttons found in the action

Solutions: Add at least one button to actions block; use type: "button" for interactive buttons

BLT1057 - INVALID_FILE_URL​

HTTP Status: 400 Bad Request | Error: Invalid URL: <fileUrl>

Solutions: Provide valid URL with protocol: https://example.com/file.pdf; verify template variable contains valid URL; test URL in browser first

BLT1058 - FILE_NOT_FOUND​

HTTP Status: 404 Not Found | Error: File not found: <fileUrl>

Solutions: Verify file exists at URL; check file wasn't deleted; use permanent URL instead of temporary; ensure file is publicly accessible

BLT1059 - UNABLE_TO_DETERMINE_FILE_SIZE​

HTTP Status: 400 Bad Request | Error: Could not determine file size for: <fileUrl>

Solutions: Use file hosting that provides Content-Length header; upload to Boltic Storage first (known size); use different file URL

BLT1060 - SIZE_EXCEEDS_LIMIT​

HTTP Status: 400 Bad Request | Error: Total file size exceeds 1 GB limit

Solutions: Reduce file sizes or compress files; split into multiple messages; share cloud storage link instead of uploading; remove unnecessary files

BLT1061 - FAILED_TO_FETCH_FILE_DETAILS​

HTTP Status: 400 Bad Request | Error: Failed to fetch file details: <error>

Solutions: Verify file URL is accessible; check network connectivity; ensure file is publicly accessible; use authenticated URL if needed

BLT1062 - FAILED_TO_GET_UPLOAD_URL​

HTTP Status: 400 Bad Request | Error: Failed to get upload URL: <slack_error>

Solutions: Verify Slack token has files:write scope; check file name and size are valid; retry after a few moments (rate limiting); check Slack API status

BLT1063 - FILE_UPLOAD_FAILED​

HTTP Status: 400/500 | Error: File upload failed: <reason>

Solutions: Retry workflow execution; check file integrity; verify network stability; reduce file size if possible

BLT1065 - CUSTOM_BODY_PARSING_ERROR​

HTTP Status: 400 Bad Request | Error: Failed to parse body for custom Slack operation

Solutions: Validate JSON syntax; check template variable outputs; use JSON validator tool; test with static body first

BLT1066 - INVALID_URL​

HTTP Status: 400 Bad Request | Error: The provided URL for custom Slack operation is invalid

Solutions: Use full Slack API URL or relative endpoint; include protocol if using full URL; verify template variables contain valid URLs

BLT1129 - FIND_USERS_FROM_EMAILS_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error finding users from emails: [error details]

Description: Failed to find Slack user IDs from provided email addresses. This occurs when looking up users by email for mentions or user-specific operations.

Common Causes: Email addresses don't match any Slack workspace users; invalid email format; Slack API rate limits exceeded; insufficient permissions; users not found in workspace

Solutions:

  1. Verify email addresses: Ensure emails match users in your Slack workspace

  2. Check email format: Use valid email format (e.g., [email protected])

  3. Verify permissions: Ensure Slack app has users:read.email scope

  4. Handle missing users: Add error handling for users not found in workspace

  5. Retry operation: Wait and retry if rate limited

Example:

// ❌ Wrong: { "emails": ["invalid-email", "[email protected]"] }
// ✅ Correct: { "emails": ["[email protected]"] }

API​

BLT1014 - INVALID_URL​

HTTP Status: 400 Bad Request | Error: The provided URL is not valid.

Description: API request URL is invalid, malformed, empty, or missing protocol.

Common Causes: Missing protocol: api.example.com instead of https://api.example.com; invalid characters or spaces in URL; template variable resolves to empty/invalid URL

Solutions: Include protocol: https://api.example.com; verify template variables contain valid URL parts; encode special characters properly; test URL in browser/API client first

Example:

// ❌ Wrong: { "url": "api.example.com/endpoint" }
// ✅ Correct: { "url": "https://api.example.com/endpoint" }

BLT1069 - BODY_PARSING_ERROR​

HTTP Status: 400 Bad Request | Error: Failed to parse the request body

Description: Request body has invalid JSON syntax or template interpolation created malformed JSON.

Common Causes: Invalid JSON structure: missing quotes, extra commas; unescaped quotes in string values; template variables contain invalid JSON; wrong body type selected (JSON vs form-data)

Solutions: Validate JSON syntax using JSON validator; check template variable outputs; ensure body type matches content (JSON, form-data, XML); properly escape special characters in strings

Example:

// ❌ Wrong - Missing comma: { "name": "John" "age": 30 }
// ✅ Correct: { "name": "John", "age": 30 }

Custom​

BLT1011 - DEFINITION_NOT_FOUND​

HTTP Status: 404 Not Found | Error: Definition not found

Description: Operation definition for custom integration doesn't exist or was deleted.

Common Causes: Incorrect operation name; operation was deleted/renamed; typo in resource.operation format

Solutions: Verify operation exists in integration settings; check integration documentation; confirm operation format: resource.operation; re-configure activity with correct operation

Example:

// ❌ Wrong: { "operation": "users.getNonExistentUser" }
// ✅ Correct: { "operation": "users.getUser" }

BLT1073 - REQUEST_DEFINITION_MISSING​

HTTP Status: 400 Bad Request | Error: Request definition is missing

Solutions: Verify activity has proper configuration; check workflow definition is valid; re-configure the activity if needed

BLT1074 - HTTP_METHOD_REQUIRED​

HTTP Status: 400 Bad Request | Error: HTTP method is required in request definition

Solutions: Add valid HTTP method: GET, POST, PUT, DELETE, or PATCH; update integration operation definition

BLT1075 - INVALID_URL​

HTTP Status: 400 Bad Request | Error: The provided URL is not valid: <finalUrl>

Solutions: Ensure URL starts with http:// or https://; verify template variables have valid values; check URL encoding for special characters

BLT1076 - INTEGRATION_SLUG_REQUIRED​

HTTP Status: 400 Bad Request | Error: Integration slug is required

Solutions: Select an integration in activity configuration; verify integration exists and is active; ensure integration slug is non-empty string

BLT1077 - OPERATION_REQUIRED​

HTTP Status: 400 Bad Request | Error: Operation name is required

Solutions: Select valid operation from dropdown; ensure operation format: resource.operation; verify integration has available operations

BLT1078 - INVALID_OPERATION_FORMAT​

HTTP Status: 400 Bad Request | Error: Operation format is invalid

Description: Operation format must be resource.operation but doesn't match this pattern.

Solutions: Use format: resource.operation (e.g., users.getUser); ensure both parts are non-empty; select from dropdown instead of manual entry

Example:

// ❌ Wrong: { "operation": "usersgetUser" }
// ✅ Correct: { "operation": "users.getUser" }

BLT1079 - ENTITY_ID_REQUIRED​

HTTP Status: 400 Bad Request | Error: Entity ID is required

Solutions: This is typically a system error - contact support; verify workflow was triggered correctly; check workflow execution logs

BLT1080 - PROPERTIES_REQUIRED​

HTTP Status: 400 Bad Request | Error: Activity properties are required

Solutions: Configure activity with required properties; ensure all required fields are filled; save activity configuration properly

BLT1084 - BODY_PARSING_ERROR​

HTTP Status: 400 Bad Request | Error: Failed to parse request body

Solutions: Validate JSON syntax; check template variable outputs; ensure proper JSON structure; test with static body first

BLT1086 - GRAPHQL_VARIABLES_PARSING_ERROR​

HTTP Status: 400 Bad Request | Error: Failed to parse GraphQL variables

Solutions: Validate GraphQL variables JSON syntax; check variable types match schema; ensure proper JSON structure

BLT1088 - OPERATION_FAILED​

HTTP Status: 500 Internal Server Error | Error: Operation failed

Solutions: Check API endpoint is accessible; verify authentication credentials; review API response for error details; retry operation

Default Errors​

BLT1007 - INPUT_DATA_EMPTY​

HTTP Status: 400 Bad Request | Error: Your Input data is Empty.

Description: Activity receives null, undefined, or empty input data when data is required.

Common Causes: Previous activity didn't return any data; incorrect data mapping in workflow configuration; missing trigger payload

Solutions: Verify previous activity returns valid data; check workflow data mapping configuration; ensure trigger payload includes required fields

BLT1008 - JSON_PARSING_ERROR​

HTTP Status: 400 Bad Request | Error: JSON parsing failed

Description: Failed to parse a JSON string into a valid object.

Common Causes: Invalid JSON syntax: missing quotes, trailing commas, single quotes instead of double quotes; unescaped special characters

Solutions: Validate JSON syntax using JSON validator; check for proper escaping of special characters; use template variables correctly (e.g., {{variable}}); ensure dynamic data is properly formatted

BLT1024 - GET_DATA_FAILED​

HTTP Status: 500 Internal Server Error | Error: Failed to fetch integration data: <original_error>

Description: Failed to retrieve integration authentication data from the system.

Common Causes: Integration service (Tesseract) is down; network timeout or connection errors; invalid entity_id or integration_id

Solutions: Check integration service health; verify network connectivity; confirm entity_id and integration_id are valid; check service logs for detailed error information

BLT1025 - REFRESH_INTEGRATION_DATA_FAILED​

HTTP Status: 500 Internal Server Error | Error: Failed to refresh integration data

Description: Failed to refresh OAuth tokens or integration credentials.

Common Causes: OAuth refresh token has been revoked; user disconnected the integration; token refresh endpoint is unavailable

Solutions: Re-authenticate the integration; check if user has revoked access; verify integration credentials are still valid; contact support if issue persists

BLT1070 - GET_DATA_EMPTY​

HTTP Status: 404 Not Found | Error: Integration data is empty or invalid

Description: Integration data was retrieved but is empty or contains no valid credentials.

Common Causes: Integration authentication flow was not completed; credentials were deleted or corrupted

Solutions: Re-authenticate the integration; delete and recreate the integration connection; verify integration data in database

BLT1071 - REFRESH_INTEGRATION_DATA_EMPTY​

HTTP Status: 500 Internal Server Error | Error: Integration data is empty after refresh

Description: Token refresh succeeded but returned empty or invalid data.

Solutions: Re-authenticate the integration; check integration service status; verify API response structure; review integration service logs

Converter​

BLT1006 - TO_AND_FROM_TYPE_REQUIRED​

HTTP Status: 400 Bad Request | Error: From and To type are required

Description: Converter activity requires both source (from) and target (to) data types to be specified.

Solutions: Specify both source and target data types; valid types: json, xml, csv, yaml, etc.; check converter activity configuration panel

BLT1009 - QUERY_EMPTY​

HTTP Status: 400 Bad Request | Error: Query can't be empty.

Description: A query or conversion expression is empty when a value is required.

Common Causes: Empty query field in configuration; variable interpolation resulted in empty string; missing template variable value

Solutions: Provide a valid query expression; verify template variables have values; check query syntax for the data type being converted

BLT1010 - NOT_SUPPORTED_DATA_CONVERSION​

HTTP Status: 400 Bad Request | Error: Data conversion not supported from <from_type> to <to_type>

Description: The requested data type conversion is not supported.

Solutions: Check supported conversion pairs in documentation; use intermediate conversion steps if needed; verify data type compatibility

BLT1120 - JSON_PARSING_ERROR​

HTTP Status: 400 Bad Request | Error: JSON parsing failed

Solutions: Validate JSON syntax; check template variable outputs; ensure proper JSON structure

BLT1101 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Converter activity: <error>

Solutions: Check input data format; verify conversion types are valid; review error details in logs

Email​

BLT1026 - NO_RECIPIENT_FOUND​

HTTP Status: 400 Bad Request | Error: No Recipient found

Description: Similar to Gmail NO_RECIPIENT_FOUND but for generic Email activity.

Solutions: Add at least one recipient email address; verify template variables contain email addresses; check email trigger data includes recipients; validate email address format

BLT1027 - ATTACHMENT_SIZE_EXCEEDS_LIMIT​

HTTP Status: 400 Bad Request | Error: Total attachment size exceeds 25 MB limit

Description: Similar to Gmail ATTACHMENT_SIZE_EXCEEDS_LIMIT but for generic Email activity.

Solutions: Reduce attachment sizes; compress files before attaching; use cloud storage links instead of attachments; split into multiple emails

BLT1099 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Email Activity: <error>

Solutions: Check email provider integration; verify credentials; review error details in logs

Execute Workflow​

BLT1015 - CHILD_WORKFLOW_SELECTION_REQUIRED​

HTTP Status: 400 Bad Request | Error: Child workflow selection is required for this activity execution.

Description: Child workflow must be selected but no workflow ID was provided.

Solutions: Select a child workflow from the dropdown; ensure selected workflow exists and is active; save activity configuration after selection

BLT1016 - NO_TRIGGER_NODE_FOUND​

HTTP Status: 400 Bad Request | Error: No trigger node found in the child workflow.

Description: The child workflow has no trigger node, which is required for execution.

Solutions: Add a trigger node to the child workflow; use HTTP trigger for synchronous child workflows; use default trigger for asynchronous child workflows

BLT1017 - CHILD_WORKFLOW_NOT_FOUND​

HTTP Status: 400 Bad Request | Error: Workflow with <id> not found.

Description: The specified child workflow does not exist or cannot be accessed.

Solutions: Verify child workflow exists in the same organization; select a different child workflow; re-create the deleted workflow if needed; check workflow access permissions

BLT1018 - CHILD_WORKFLOW_HAS_NO_NODES​

HTTP Status: 400 Bad Request | Error: Child workflow has no nodes.

Description: The child workflow exists but contains no activity nodes.

Solutions: Add activity nodes to the child workflow; configure the child workflow properly; select a different child workflow

BLT1085 - BODY_PARSING_ERROR​

HTTP Status: 400 Bad Request | Error: Failed to parse payload

Solutions: Validate payload JSON syntax; check template variable outputs; ensure proper JSON structure

BLT1100 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from ExecuteChildWorkflow activity: <error>

Solutions: Check child workflow configuration; verify workflow execution permissions; review error details in logs

Google Sheets Read​

BLT1031 - INVALID_RANGE​

HTTP Status: 400 Bad Request | Error: Invalid range provided <range>

Description: The cell range specified for reading Google Sheets is invalid.

Common Causes: Range format doesn't match A1 notation; range is empty or undefined; invalid cell references

Solutions: Use valid A1 notation (e.g., A1:Z100); remove extra spaces from range; verify template variables contain valid ranges; include sheet name if needed (e.g., Sheet1!A1:B10)

Valid formats: A1:B10 (specific range), Sheet1!A1:B10 (with sheet name), A:A (entire column), 1:1 (entire row)

BLT1032 - LOOKUP_COLUMN_REQUIRED​

HTTP Status: 400 Bad Request | Error: lookupColumn is required

Solutions: Specify the column to search in (e.g., "Email", "A", "1"); ensure template variable has a value; verify column exists in the sheet

BLT1033 - LOOKUP_VALUE_REQUIRED​

HTTP Status: 400 Bad Request | Error: lookupValue is required

Solutions: Provide the value to search for; verify template variable contains data; check previous activity output

BLT1034 - INVALID_LOOKUP_COLUMN​

HTTP Status: 400 Bad Request | Error: valid column identifier

Solutions: Use valid column letters (A-Z, AA-ZZ); or use exact header name from first row; verify column exists in target sheet; check spelling of column name

BLT1035 - REQUIRED_GOOGLE_SHEET_DATA_MISSING​

HTTP Status: 400 Bad Request | Error: Required data for Google Sheets operation is missing

Description: Required data for Google Sheets operation is missing (document ID, sheet name, etc.).

Solutions: Select a valid Google Sheets document; provide sheet name; verify all required fields are filled; ensure sheet still exists and is accessible

BLT1107 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Google Sheets Read Activity: <error>

Solutions: Check Google Sheets integration; verify credentials; review error details in logs

BLT1132 - CREDENTIALS_NOT_AVAILABLE​

HTTP Status: 400 Bad Request | Error: Credentials not available for id - [credential_id]

Description: Google Sheets credentials are missing, invalid, or not accessible for the specified credential ID.

Common Causes: Credential ID doesn't exist; credentials were deleted or revoked; OAuth token expired; insufficient permissions to access credentials; integration not properly connected

Solutions:

  1. Reconnect integration: Disconnect and reconnect Google Sheets integration

  2. Verify credential ID: Ensure credential ID matches an existing integration

  3. Check OAuth status: Verify OAuth token is valid and not expired

  4. Grant permissions: Ensure Google Sheets API permissions are granted

  5. Use secret override: If using secret override, verify the override secret is valid

Google Sheets Write​

BLT1036 - NO_HEADERS_FOUND​

HTTP Status: 400 Bad Request | Error: No headers found

Description: No column headers were found in the sheet for write operation.

Solutions: Add headers to first row of sheet; verify sheet has data; ensure headers are in row 1; use append mode if sheet is empty

BLT1037 - NO_VALID_HEADERS_FOUND​

HTTP Status: 400 Bad Request | Error: No valid headers found

Description: Headers exist but none are valid (all empty strings or whitespace).

Solutions: Ensure all header cells have non-empty values; remove leading/trailing whitespace; use alphanumeric characters in headers; avoid special characters in header names

BLT1038 - REQUIRED_GOOGLE_SHEET_DATA_MISSING​

HTTP Status: 400 Bad Request | Error: Required Google Sheet data missing

Solutions: Provide document ID; specify sheet name; add data to write; verify all required fields are configured

BLT1039 - ROW_NUMBER_SHOULD_BE_A_NUMBER​

HTTP Status: 400 Bad Request | Error: Row number should be a number

Solutions: Ensure row number is a valid integer; convert string to number if using template variables; use numeric values only (1, 2, 3, etc.)

BLT1040 - ROW_NUMBER_REQUIRED​

HTTP Status: 400 Bad Request | Error: Row number is required

Solutions: Specify which row to update/delete; provide row number (1-based index); verify template variable has value

BLT1041 - NO_DATA_TO_APPEND​

HTTP Status: 400 Bad Request | Error: No data to append

Solutions: Provide data to write to sheet; verify template variables have values; check previous activity output; ensure data mapping is correct

BLT1108 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Google Sheets Write activity: <error>

Solutions: Check Google Sheets integration; verify credentials; review error details in logs

BLT1131 - CREDENTIALS_NOT_AVAILABLE​

HTTP Status: 400 Bad Request | Error: Credentials not available for id - [credential_id]

Description: Google Sheets credentials are missing, invalid, or not accessible for the specified credential ID.

Common Causes: Credential ID doesn't exist; credentials were deleted or revoked; OAuth token expired; insufficient permissions to access credentials; integration not properly connected

Solutions:

  1. Reconnect integration: Disconnect and reconnect Google Sheets integration

  2. Verify credential ID: Ensure credential ID matches an existing integration

  3. Check OAuth status: Verify OAuth token is valid and not expired

  4. Grant permissions: Ensure Google Sheets API permissions are granted

  5. Use secret override: If using secret override, verify the override secret is valid

GraphQL​

BLT1042 - QUERY_REQUIRED​

HTTP Status: 400 Bad Request | Error: GraphQL query is required.

Description: GraphQL query is required but was not provided.

Solutions: Write a valid GraphQL query; include query, mutation, or subscription; verify query syntax is correct; test query in GraphQL playground first

Example valid query:

query GetUser($id: ID!) {
  user(id: $id) {
    name
    email
  }
}

BLT1043 - INVALID_URL​

HTTP Status: 400 Bad Request | Error: The provided URL is not valid: <url>

Description: The GraphQL endpoint URL is invalid or malformed.

Solutions: Provide valid GraphQL endpoint; include protocol: https://api.example.com/graphql; verify template variables contain valid URLs; test endpoint URL manually first

BLT1087 - GRAPHQL_VARIABLES_PARSING_ERROR​

HTTP Status: 400 Bad Request | Error: Failed to parse GraphQL variables

Solutions: Validate GraphQL variables JSON syntax; check variable types match schema; ensure proper JSON structure

If​

BLT1044 - NO_BRANCHES_FOUND​

HTTP Status: 400 Bad Request | Error: No branches found for IF Activity

Description: If activity has no conditional branches configured.

Solutions: Add at least one If or ElseIf branch; configure conditions for each branch; add Else branch for default case; save configuration after adding branches

BLT1045 - NO_CONDITIONS_FOUND​

HTTP Status: 400 Bad Request | Error: No conditions found for branch "<ref>"

Description: A branch in the If activity has no conditions defined.

Solutions: Add at least one condition to each branch; define condition logic (equals, contains, greater than, etc.); provide values to compare; save configuration after adding conditions

BLT1110 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from If Activity: <error>

Solutions: Check condition expressions; verify data types match; review error details in logs

BLT1130 - INVALID_OPERATOR​

HTTP Status: 400 Bad Request | Error: Invalid operator

Description: If activity contains an invalid logical operator between conditions. Only "AND" and "OR" operators are supported.

Common Causes: Using unsupported operators (e.g., "NOT", "XOR", "NAND"); typo in operator name; case sensitivity issues; template variable resolves to invalid operator

Solutions:

  1. Use valid operators: Only use "AND" or "OR" (case-sensitive)

  2. Check spelling: Ensure operator is spelled correctly: "AND" or "OR"

  3. Fix template variables: Ensure {{result.operator}} resolves to "AND" or "OR"

  4. Review condition structure: Verify condition array and operators array are properly aligned

Example:

// ❌ Wrong: { "operators": ["AND", "NOT", "OR"] }
// ✅ Correct: { "operators": ["AND", "OR"] }

Loop​

BLT1046 - INPUT_MUST_BE_AN_ARRAY​

HTTP Status: 400 Bad Request | Error: Loop input must be an array. Received: <type>

Description: Loop activity requires an array as input but received a non-array value.

Common Causes: Loop input is an object, string, number, or null; template variable doesn't resolve to array; previous activity returned non-array data

Solutions: Ensure loop input is an array: [item1, item2, item3]; convert single object to array: [object]; verify template variable points to array field; check previous activity output structure

Valid input examples:

[1, 2, 3, 4, 5]
[{"name": "John"}, {"name": "Jane"}]
["apple", "banana", "orange"]

BLT1112 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Loop Activity: <error>

Solutions: Check loop input data structure; verify array format; review error details in logs

Switch​

BLT1067 - NO_CASES_FOUND​

HTTP Status: 400 Bad Request | Error: No cases found for the Switch to execute

Description: Switch activity has no case branches configured.

Solutions: Add at least one case to the switch; define case values and types; add default case for unmatched values; complete configuration before saving

BLT1128 - CONDITION_NOT_FOUND​

HTTP Status: 400 Bad Request | Error: Condition not found in Switch

Description: Switch activity is missing the condition property required to evaluate which case to execute.

Common Causes: Condition property not configured in workflow; condition property is empty or null; template variable resolves to empty value

Solutions:

  1. Add condition property: Configure the condition field in Switch activity settings

  2. Check template variables: Ensure {{result.condition}} contains a valid value

  3. Use static condition: Test with a static condition value first (e.g., "value1")

Example:

// ❌ Wrong: { "condition": null }
// ✅ Correct: { "condition": "{{result.status}}" }

BLT1068 - INVALID_SWITCH_CONDITION_RESULT​

HTTP Status: 400 Bad Request | Error: Switch condition must result in a valid number or string value

Description: Switch condition must evaluate to a string or number but returned invalid type (object, array, boolean).

Common Causes: Condition references complex object; using boolean where string/number expected; array or object in switch condition

Solutions: Ensure condition returns string or number; convert complex types to string/number; use toString() or type conversion; check condition expression logic

Valid condition results: Strings: "approved", "pending"; Numbers: 1, 2, 404

Invalid condition results: Objects: {status: "approved"}; Arrays: ["approved"]; Booleans: true, false (use If activity instead)

BLT1117 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Switch Activity: <error>

Solutions: Check switch condition expression; verify case values match condition result; review error details in logs

HTTP Operations inside activities​

BLT1090 - ENDPOINT_REQUIRED​

HTTP Status: 400 Bad Request | Error: Endpoint is required for custom operation

Description: Endpoint URL is missing or empty for HTTP operation.

Solutions: Provide endpoint URL in activity configuration; verify endpoint field is not empty; check template variables contain valid endpoint

BLT1091 - METHOD_REQUIRED​

HTTP Status: 400 Bad Request | Error: Method is required for custom operation

Description: HTTP method (GET, POST, PUT, DELETE, PATCH) is missing.

Solutions: Select HTTP method: GET, POST, PUT, DELETE, or PATCH; verify method field is configured; check activity configuration

BLT1092 - INVALID_URL​

HTTP Status: 400 Bad Request | Error: The provided URL is not valid.

Description: Endpoint URL is invalid, malformed, or missing protocol.

Solutions: Ensure URL starts with http:// or https://; verify template variables contain valid URLs; check URL encoding for special characters; test URL manually

BLT1093 - REQUEST_FAILED​

HTTP Status: 500 Internal Server Error | Error: HTTP request failed

Description: HTTP request to endpoint failed due to network error, timeout, or API error.

Solutions: Check endpoint is accessible; verify network connectivity; check API response for error details; retry operation; verify authentication credentials

BLT1094 - BODY_PARSING_ERROR​

HTTP Status: 400 Bad Request | Error: Failed to parse request body

Description: Request body has invalid JSON syntax or parsing failed.

Solutions: Validate JSON syntax; check template variable outputs; ensure proper JSON structure; test with static body first

Function​

BLT1028 - UNSUPPORTED_LANGUAGE​

HTTP Status: 400 Bad Request | Error: Unsupported language: <language>

Description: Programming language specified is not supported. Only javascript and python are supported.

Common Causes: Typo in language name; using unsupported language; language field empty

Solutions: Use javascript or python as language value; check spelling of language name; verify language is supported

Example:

// ❌ Wrong: { "language": "java" }
// ✅ Correct: { "language": "javascript" }

BLT1072 - EXECUTION_ERROR​

HTTP Status: 500 Internal Server Error | Error: Function execution error

Description: An error occurred during function execution in the VM sandbox.

Common Causes: Runtime error in user code; uncaught exception; syntax error; timeout during execution; accessing undefined variables

Solutions: Debug function code for errors; add try-catch blocks for error handling; check function logs for error details; verify all variables are defined; ensure function completes within timeout (60s)

BLT1103 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Function activity: <error>

Solutions: Check function code syntax; verify function logic; review error details in logs; test function with sample data

Google Calendar​

BLT1029 - INVALID_DATE_FORMAT​

HTTP Status: 400 Bad Request | Error: Invalid date format

Description: Date or time value provided is not in a valid format. Google Calendar API requires ISO 8601 format.

Common Causes: Incorrect date format in configuration; template variable has invalid date; missing timezone information; using locale-specific format instead of ISO

Solutions: Use ISO 8601 format: 2024-11-27T10:00:00Z; include timezone information; verify template variables contain valid dates; use date formatting functions to ensure consistency

Valid formats:

  • 2024-11-27T10:00:00Z (UTC)
  • 2024-11-27T10:00:00-05:00 (with offset)
  • 2024-11-27T10:00:00.000Z (with milliseconds)

Example:

// ❌ Wrong: { "start_date_time": "11/27/2024 10:00 AM" }
// ✅ Correct: { "start_date_time": "2024-11-27T10:00:00Z" }

BLT1106 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Google Calendar Activity: <error>

Solutions: Check Google Calendar integration; verify credentials; ensure OAuth token has calendar scopes; review error details in logs

BLT1134 - CREDENTIALS_NOT_AVAILABLE​

HTTP Status: 400 Bad Request | Error: Credentials not available for id - [credential_id]

Description: Google Calendar credentials are missing, invalid, or not accessible for the specified credential ID.

Common Causes: Credential ID doesn't exist; credentials were deleted or revoked; OAuth token expired; insufficient permissions to access credentials; integration not properly connected

Solutions:

  1. Reconnect integration: Disconnect and reconnect Google Calendar integration

  2. Verify credential ID: Ensure credential ID matches an existing integration

  3. Check OAuth status: Verify OAuth token is valid and not expired

  4. Grant permissions: Ensure Google Calendar API permissions are granted

  5. Use secret override: If using secret override, verify the override secret is valid

Google Meet​

BLT1030 - INVALID_DATE_FORMAT​

HTTP Status: 400 Bad Request | Error: Invalid date format

Description: Meeting date or time value is not in a valid format. Google Meet API requires ISO 8601 format.

Common Causes: Incorrect date format in meeting configuration; template variable has invalid date value; missing or wrong timezone

Solutions: Use ISO 8601 format: 2024-11-27T14:00:00Z; include explicit timezone; ensure start time is before end time; verify template variables contain valid datetime strings

Example:

// ❌ Wrong: { "start_date_time": "Tomorrow 2pm" }
// ✅ Correct: { "start_date_time": "2024-11-27T14:00:00Z" }

BLT1105 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Google Meet Activity: <error>

Solutions: Check Google Meet integration; verify credentials; ensure OAuth token has calendar scopes; review error details in logs

BLT1133 - CREDENTIALS_NOT_AVAILABLE​

HTTP Status: 400 Bad Request | Error: Credentials not available for id - [credential_id]

Description: Google Meet credentials are missing, invalid, or not accessible for the specified credential ID.

Common Causes: Credential ID doesn't exist; credentials were deleted or revoked; OAuth token expired; insufficient permissions to access credentials; integration not properly connected

Solutions:

  1. Reconnect integration: Disconnect and reconnect Google Calendar/Meet integration

  2. Verify credential ID: Ensure credential ID matches an existing integration

  3. Check OAuth status: Verify OAuth token is valid and not expired

  4. Grant permissions: Ensure Google Calendar API permissions are granted (Meet uses Calendar API)

  5. Use secret override: If using secret override, verify the override secret is valid

Mapper​

BLT1047 - BODY_PARSING_ERROR​

HTTP Status: 400 Bad Request | Error: Failed to parse mapper body JSON structure

Description: Failed to parse the mapper body JSON structure.

Common Causes: Invalid JSON in mapper configuration; template interpolation created invalid JSON; syntax error in mapper body; missing quotes, commas, or brackets

Solutions: Validate JSON syntax; check template variable outputs; use JSON validator tool; properly escape special characters; test with static data first

Example:

// ❌ Wrong - Missing comma
{ "name": "John" "age": 30 }

// ✅ Correct
{ "name": "John", "age": 30 }

BLT1113 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Mapper Activity: <error>

Solutions: Check mapper JSON structure; verify template variables; review error details in logs

Parallel​

BLT1048 - NO_OUTGOING_PORTS_FOUND​

HTTP Status: 400 Bad Request | Error: Parallel node has no outgoing ports defined

Description: Parallel activity has no outgoing paths defined to subsequent activities.

Common Causes: Parallel activity not connected to any activities; connections were deleted; workflow configuration incomplete

Solutions: Connect parallel activity to at least one subsequent activity; add parallel branches in workflow editor; ensure each branch has activities; save workflow after adding connections

BLT1114 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Parallel activity: <error>

Solutions: Check parallel activity configuration; verify outgoing ports are connected; review error details in logs

Response​

BLT1050 - FIELD_PROCESSING_ERROR​

HTTP Status: 400 Bad Request | Error: An issue occurred while processing the <field>

Description: Failed to process response headers or body fields during template variable interpolation.

Common Causes: Template variable references non-existent field; data type mismatch; invalid JSON in response body; special characters not escaped

Solutions: Verify template variables reference valid fields; check data types match expected format; validate JSON structure; ensure previous activity output exists; test with simple static values first

Example:

// ❌ Wrong - Field doesn't exist
{ "response_body": "{{result.missing_field}}" }

// ✅ Correct - Valid field
{ "response_body": "{{result.data}}" }

BLT1115 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Response activity: <error>

Solutions: Check response field configurations; verify template variables; review error details in logs

Platform FDK​

BLT1049 - BODY_PARSING_ERROR​

HTTP Status: 400 Bad Request | Error: Failed to parse request body for Fynd Platform API call

Description: Request body has invalid JSON syntax or template interpolation created malformed JSON.

Common Causes: Invalid JSON structure in body; template variables contain invalid data; missing quotes or commas; unescaped special characters

Solutions: Validate JSON syntax; check template variable outputs; properly escape special characters; use JSON validator; test with static data first

BLT1081 - INTEGRATION_SLUG_REQUIRED​

HTTP Status: 400 Bad Request | Error: Integration slug is required

Description: Integration slug (identifier) is missing or empty for Platform FDK activity.

Solutions: Select an integration in activity configuration; verify integration exists and is active; ensure integration slug is non-empty string

BLT1089 - FDK_OPERATION_FAILED​

HTTP Status: 500 Internal Server Error | Error: Fynd Platform FDK operation failed

Description: Fynd Platform FDK operation execution failed.

Solutions: Check API endpoint is accessible; verify authentication credentials; review API response for error details; check Fynd Platform API status; retry operation

Application FDK​

BLT1119 - FORBIDDEN​

HTTP Status: 403 Forbidden | Error: Error from Application Client: <error>

Description: Forbidden (403) error from Application Client API. Access denied due to insufficient permissions.

Common Causes: Invalid or expired API credentials; insufficient permissions for requested operation; API key lacks required scopes

Solutions: Verify API credentials are valid; check API key has required permissions; regenerate API key if needed; contact API administrator for access

BLT1082 - INTEGRATION_SLUG_REQUIRED​

HTTP Status: 400 Bad Request | Error: Integration slug is required

Description: Integration slug (identifier) is missing or empty for Application FDK activity.

Solutions: Select an integration in activity configuration; verify integration exists and is active; ensure integration slug is non-empty string

BLT1083 - BODY_PARSING_ERROR​

HTTP Status: 400 Bad Request | Error: Failed to parse request body

Description: Request body has invalid JSON syntax or parsing failed.

Solutions: Validate JSON syntax; check template variable outputs; ensure proper JSON structure; test with static body first

BLT1095 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Application Client: <error>

Solutions: Check Application FDK integration; verify credentials; review error details in logs; test API access outside workflow

Boltic Storage​

BLT1020 - INVALID_FOLDER_NAME​

HTTP Status: 400 Bad Request | Error: Invalid folder name

Description: Folder name contains invalid characters or is in an invalid format.

Common Causes: Using special characters: !@#$%^&*()+{}[]:;<>,.?~; forward slashes in folder name; empty folder name; template variable contains invalid characters

Solutions: Use only letters, numbers, spaces, underscores (_), and hyphens (-); remove special characters from folder name; avoid using forward slashes (/) in folder names; validate template variable outputs

Example:

// ❌ Wrong: { "folder_name": "My/Folder@2024" }
// ✅ Correct: { "folder_name": "My_Folder_2024" }

BLT1021 - UNKNOWN_EVENT_TYPE​

HTTP Status: 400 Bad Request | Error: Unknown event type: <event_type>

Description: Storage activity event type is not recognized or supported.

Common Causes: Typo in event type configuration; using deprecated event type; invalid activity configuration

Solutions: Use valid event types: create_folder, upload_file; check activity documentation for supported event types; re-configure activity with correct event type

Example:

// ❌ Wrong: { "event": "createDirectory" }
// ✅ Correct: { "event": "create_folder" }

BLT1097 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Boltic Storage activity: <error>

Solutions: Check storage configuration; verify file/folder permissions; review error details in logs

BLT1121 - INVALID_FOLDER_PATH_CHARACTERS​

HTTP Status: 400 Bad Request | Error: Folder path contains invalid characters: [!@#$%^&*()+{}[]:;<>,.?~]

Description: Folder path contains special characters that are not allowed in GCS folder names. Only alphanumeric characters, spaces, underscores, and hyphens are permitted.

Common Causes: Using special characters in folder path template variables; dynamic interpolation resolves to invalid characters; copying folder paths from other systems with special characters

Solutions:

  1. Remove special characters: Use only letters, numbers, spaces, underscores (_), and hyphens (-)

  2. Sanitize template variables: Ensure {{result.folder_path}} doesn't contain special characters

  3. Use valid folder names: Replace special characters with underscores or hyphens

Example:

// ❌ Wrong: { "folder_path": "my-folder@2024!" }
// ✅ Correct: { "folder_path": "my-folder-2024" }

BLT1122 - INVALID_FILE_NAME_SLASH​

HTTP Status: 400 Bad Request | Error: '/' in file name is not allowed

Description: File name contains a forward slash character, which is not allowed as it's reserved for path separators.

Common Causes: Using folder path syntax in file name field; template variable contains path instead of filename; copying full path instead of just filename

Solutions:

  1. Use only filename: Provide just the filename without any path separators

  2. Separate folder and filename: Use folder_path for directory and file_name for filename only

  3. Fix template variables: Ensure {{result.file_name}} contains only filename, not full path

Example:

// ❌ Wrong: { "file_name": "documents/report.pdf" }
// ✅ Correct: { "file_name": "report.pdf", "folder_path": "documents" }

BLT1123 - INVALID_FOLDER_NAME_PATTERN​

HTTP Status: 400 Bad Request | Error: Folder name is invalid: only letters, numbers, spaces, underscores (_), and hyphens (-) are allowed.

Description: Folder name doesn't match the required pattern. Only alphanumeric characters, spaces, underscores, and hyphens are allowed.

Common Causes: Using special characters or symbols in folder name; template variable resolves to invalid characters; non-ASCII characters in folder name

Solutions:

  1. Use valid characters only: Limit to A-Z, a-z, 0-9, spaces, underscores, and hyphens

  2. Sanitize folder names: Replace invalid characters before creating folder

  3. Validate template output: Ensure {{result.folder_name}} produces valid folder name

Example:

// ❌ Wrong: { "folder_name": "My Folder #2024" }
// ✅ Correct: { "folder_name": "My Folder 2024" }

BLT1124 - CREATE_FOLDER_API_ERROR​

HTTP Status: 500 Internal Server Error (or error response status) | Error: An error occurred while creating folder or API error message

Description: API call to create folder in GCS failed. This could be due to API errors, authentication issues, or service unavailability.

Common Causes: Invalid or expired credentials; GCS API rate limits exceeded; network connectivity issues; insufficient permissions; folder already exists with different permissions

Solutions:

  1. Check credentials: Verify GCS credentials are valid and have proper permissions

  2. Retry operation: Wait and retry if rate limited

  3. Verify permissions: Ensure service account has storage.objects.create permission

  4. Check folder existence: Verify folder doesn't already exist with conflicting settings

BLT1125 - CREATE_FOLDER_ERROR​

HTTP Status: 500 Internal Server Error | Error: An error occurred while creating folder or error message from caught exception

Description: General error occurred during folder creation process, not specifically from API call.

Common Causes: Invalid input parameters; template interpolation errors; validation failures; unexpected errors in folder creation logic

Solutions:

  1. Validate inputs: Check folder name and path parameters are valid

  2. Check template variables: Ensure all template variables resolve correctly

  3. Review error details: Check full error message for specific cause

BLT1126 - UPLOAD_FILE_API_ERROR​

HTTP Status: 500 Internal Server Error (or error response status) | Error: An error occurred while uploading file or API error message

Description: API call to upload file to GCS failed. This could be due to API errors, authentication issues, file size limits, or service unavailability.

Common Causes: Invalid or expired credentials; file size exceeds limits; GCS API rate limits exceeded; network connectivity issues; insufficient permissions; invalid file content or format

Solutions:

  1. Check credentials: Verify GCS credentials are valid and have proper permissions

  2. Verify file size: Ensure file doesn't exceed GCS upload limits

  3. Retry operation: Wait and retry if rate limited

  4. Verify permissions: Ensure service account has storage.objects.create permission

  5. Check file format: Ensure file content is valid and properly formatted

BLT1127 - UPLOAD_FILE_ERROR​

HTTP Status: 500 Internal Server Error | Error: An error occurred while uploading file or error message from caught exception

Description: General error occurred during file upload process, not specifically from API call.

Common Causes: Invalid input parameters; template interpolation errors; file content processing errors; validation failures; unexpected errors in upload logic

Solutions:

  1. Validate inputs: Check file name, content, and folder path parameters are valid

  2. Check template variables: Ensure all template variables resolve correctly

  3. Verify file content: Ensure file content is properly formatted (base64, JSON, CSV, etc.)

  4. Review error details: Check full error message for specific cause

Boltic Table​

BLT1022 - INVALID_RECORD_ID​

HTTP Status: 400 Bad Request | Error: Record id is invalid

Description: Record ID provided for table operation is invalid or missing.

Common Causes: Missing record ID in update/delete operations; template variable for record ID is empty; incorrect field mapping; record was already deleted

Solutions: Provide a valid record ID; verify record exists in the table; check template variable contains valid ID; use correct field mapping for record ID

Example:

// ❌ Wrong: { "record_id": "" }
// ✅ Correct: { "record_id": "12345" }

BLT1023 - RESPONSE_BODY_NOT_AVAILABLE​

HTTP Status: 500 Internal Server Error | Error: Response body is not available

Description: Expected response body from table operation is missing or unavailable.

Common Causes: Table API returned success but no data; response structure is incomplete; network error during response

Solutions: Retry the operation; check table service status; verify network connectivity; review service logs for details

BLT1098 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Boltic Table Activity: <error>

Solutions: Check table configuration; verify table exists; review error details in logs; check table service status

Ask Agent​

BLT1019 - FAILED_TO_CREATE_COPILOT_INTEGRATION​

HTTP Status: 500 Internal Server Error | Error: Failed to create Copilot AI integration

Description: Failed to create or initialize the Copilot AI integration for the Ask Agent activity.

Common Causes: Invalid or expired Copilot API key; Copilot service outage; network connectivity issues; configuration error in Copilot settings

Solutions: Verify Copilot API key is valid; check Copilot service status; review integration configuration; contact support if issue persists

BLT1096 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Ask Agent activity: <error>

Solutions: Check Copilot integration configuration; verify API credentials; review error details in logs

Browserbase​

BLT1102 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Browserbase activity: <error>

Description: Catch-all error for unexpected Browserbase activity failures.

Solutions: Check Browserbase integration configuration; verify API credentials; check Browserbase service status; review error details in logs; retry operation

GPT​

BLT1109 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from GPT activity: <error>

Description: Catch-all error for unexpected GPT activity failures.

Solutions: Check GPT integration configuration; verify API key is valid; check OpenAI API status; review error details in logs; verify API rate limits

Log Console​

BLT1111 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Log Console activity: <error>

Description: Catch-all error for unexpected Log Console activity failures.

Solutions: Check log message format; verify template variables; review error details in logs

Serverless​

BLT1116 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Serverless activity: <error>

Description: Catch-all error for unexpected Serverless activity failures.

Solutions: Check serverless function configuration; verify function exists and is deployed; check function logs; review error details; verify function timeout settings

Template​

BLT1118 - UNKNOWN_ERROR​

HTTP Status: 500 Internal Server Error | Error: Error from Template activity: <error>

Description: Catch-all error for unexpected Template activity failures.

Solutions: Check template syntax; verify template variables exist; review error details in logs; test template with sample data

General Troubleshooting Tips​

  1. Check workflow execution logs for full error context
  2. Verify all previous activities completed successfully
  3. Review the exact data structure in execution result
  4. Test with static data first, then add dynamic content
  5. Validate JSON syntax before using in activities
  6. Ensure template variables contain expected data types
  7. Verify integrations are properly connected and authenticated
  8. Check API rate limits and retry logic

Support​

If the issue persists after trying the above solutions:

  1. Check workflow execution logs for full error context
  2. Verify all previous activities completed successfully
  3. Review the exact data structure in execution result
  4. Contact support with:
    • Error code: BLT####
    • Workflow ID
    • Execution ID
    • Relevant activity configurations
    • Error message details