Boomi errors
Common Boomi errors, grouped by component. Open one for the exact error text, its likely causes, the fix and the official documentation.
- Errors
- 71
- Components
- 41
- Verified
- 71
- Official docs
- help.boomi.com
71 errors in 41 groups
Boomi for SAP1
Boomi Platform API7
- 400 Bad Request (Platform API)A 400 Bad Request from the Boomi Platform API means the request's format or values do not match the API schema. Read the message in the response, correct the request and resend it.
- 401 Unauthorized (Platform API)A 401 from the Boomi Platform API means authentication failed or the credentials expired. The usual causes are an expired JWT, which lasts only 5 minutes, bad Basic Auth credentials or an invalid API token.
- 403 Forbidden (Platform API)A 403 from the Boomi Platform API means the credentials are incorrect or partial for what you asked. Check the user's permissions and account access, and the credentials set in your API tool.
- 404 Not Found (Platform API)A 404 from the Boomi Platform API means the endpoint does not exist. Check the URL and the request body.
- 410 Gone (Platform API)A 410 from the Boomi Platform API means the API is retired, or the Atom you specified is offline. Bring the runtime back online, or move to the API that replaced the retired one.
- 503 Service Unavailable (Platform API)A 503 from the Boomi Platform API means the server is too busy or you exceeded the rate limit. Retry with an increasing delay.
- 504 Gateway Timeout (Platform API)A 504 from the Boomi Platform API means the client cannot reach the Atom or the server. Check that the runtime is reachable, then retry with an increasing delay.
Boomi runtime6
- IllegalStateException: exceeded active batch limitThis exception means a listener has more active batches than Maximum Number of Active Batches per Listener allows. Let batches complete before new ones start, or review that property.
- Low memory in memory poolThis container log message means the runtime's heap use went over the Low Memory Mode Threshold, so documents are flushed to disk and disk I/O rises. Increase the JVM heap if the machine has the physical RAM.
- OutOfMemoryExceptionAn OutOfMemoryException in Boomi means the runtime ran out of memory while processing, usually on large or concurrent data sets. Split or batch the data so it is not held in memory at once, and give the runtime more heap if the machine has it.
- Process discarded due to system load: execution queue maximum size reachedThis message means the node's execution queue was full, so the runtime discarded the submitted process instead of queuing it. Reduce how many executions arrive at once, or review the Maximum Queued Executions per Node and Maximum Simultaneous Executions per Node properties.
- Process exceeded maximum execution time limitThese log lines mean the runtime cancelled the execution because it ran longer than the Maximum Forked Execution Time in Cloud. Make the process finish sooner, for example by splitting the work, or review that property.
- SecurityException: Exceeded thread limitThis exception means a forked execution or an execution worker tried to use more threads than the runtime allows. Lower the parallelism in the process, or review the Maximum Execution Threads property.
Data Integration: Activate Data Flow5
- RVR-ACTIVATE-100: cannot find the connectionRVR-ACTIVATE-100 means the platform cannot find the connection a Data Flow names. Fix the connection name, or create the connection if it does not exist.
- RVR-ACTIVATE-200: failed to get metadata from the databaseRVR-ACTIVATE-200 means the platform could not retrieve metadata from the database, because the connection is invalid or the network is blocked. Verify the connection settings and the user's permission to read metadata.
- RVR-ACTIVATE-201: cannot connect to the source connectionRVR-ACTIVATE-201 means the platform cannot connect to the source connection the Data Flow uses. Check the credentials, permissions and network access, and re-authenticate if tokens or passwords changed.
- RVR-ACTIVATE-300: invalid Data Flow settingsRVR-ACTIVATE-300 means the Data Flow has missing or incorrect settings that prevent activation. Review every setting and complete the required fields.
- RVR-ACTIVATE-400: cannot activate the Data FlowRVR-ACTIVATE-400 means the platform could not activate a Data Flow because of a configuration, authentication or network issue in the connector process. Check the source and target connections first.
Data Integration: Amazon Athena2
- RVR-ATH-100: error trying to connect to AthenaRVR-ATH-100 means Data Integration could not connect to Amazon Athena, from misconfigured connection settings or missing permissions. Verify the region, workgroup and credentials, and the IAM permissions.
- RVR-ATH-200: error in query execution result (Athena)RVR-ATH-200 means a query Data Integration ran against Athena failed, from configuration, bucket permissions or the query itself. Check the S3 and Athena permissions and the SQL.
Data Integration: Amazon Redshift1
Data Integration: Amazon S31
Data Integration: Azure Blob Storage1
Data Integration: Azure SQL2
- RVR-MSS-500: Azure SQL internal errorRVR-MSS-500 is an internal error in the Azure SQL connector that points to connection setup or database configuration, most often Change Tracking or cleanup. Verify Change Tracking and re-initialize affected tables.
- RVR-MSS-501: Azure SQL external general errorRVR-MSS-501 is an external general error from the Azure SQL connector, usually server settings or network connectivity. Check the Azure SQL firewall and the credentials' rights.
Data Integration: Column mapping1
Data Integration: Configuration1
Data Integration: Data Flows1
Data Integration: Deployment3
- RVR-DEP-100: deployment package settings errorRVR-DEP-100 means the deployment package settings are wrong or incomplete. Review the package's environment variables, mappings and target settings.
- RVR-DEP-102: deployment notifications settings errorRVR-DEP-102 is a problem with the deployment notification settings. Check the notification type and recipients, and the permissions to change them.
- RVR-DEP-301: async deployment errorRVR-DEP-301 is an asynchronous operation problem while deploying Data Flows, possibly from conflicting processes. Make sure nothing else is updating the same resources, then redeploy.
Data Integration: FTP1
Data Integration: Google BigQuery1
Data Integration: IP allowlist1
Data Integration: Jira1
Data Integration: Logic2
- RVR-LGR-001: variable value exceeds maximum allowed sizeRVR-LGR-001 means a variable in a Logic Flow grew past the maximum size, usually by collecting a large data set or long concatenated text. Split the data into smaller chunks.
- RVR-LGR-002: Logic user errorRVR-LGR-002 is a user-side configuration problem in a Logic Flow. Check the flow's parameters and any recent changes.
Data Integration: Logicode1
Data Integration: Mail1
Data Integration: Microsoft SQL Server1
Data Integration: MongoDB2
- RVR-MGB-100: MongoDB JSON parsing errorRVR-MGB-100 is a JSON parsing error in the MongoDB connector, from unexpected structure, invalid syntax or badly nested data. Find the document that fails in the logs and fix or flatten its structure.
- RVR-MGB-200: MongoDB operation failureRVR-MGB-200 means a MongoDB operation failed, because of the connection configuration, an unsupported MongoDB version or a data loading issue. Verify the connection and that the server is MongoDB 3.4 or above.
Data Integration: MySQL1
Data Integration: NetSuite1
Data Integration: NetSuite RESTlets1
Data Integration: Platform1
Data Integration: PostgreSQL1
Data Integration: Python1
Data Integration: QuickBooks1
Data Integration: REST Action1
Data Integration: REST API1
Data Integration: Salesforce Marketing Cloud1
Data Integration: ServiceNow1
Data Integration: SFTP8
- RVR-SFTP-100: problem downloading a file over SFTPRVR-SFTP-100 means the SFTP storage connector could not download a file. Check the connection parameters, the authentication method and network access.
- RVR-SFTP-101: cannot create a directory over SFTPRVR-SFTP-101 means Data Integration could not create a directory on the SFTP server. Give the SFTP user permission to create directories and check the connection configuration.
- RVR-SFTPConn-100: SFTP connection error, bad credentials or permissionsRVR-SFTPConn-100 is an SFTP connection error caused by bad credentials or missing permissions. Check the username, password or key file, and that the user has SFTP access.
- RVR-SFTPConn-101: SFTP connection failureRVR-SFTPConn-101 is a connection failure to an SFTP server. Start with IP allowlisting and the authentication details, then the host, port and firewall.
- RVR-SFTPConn-102: bad SSH keys or fileRVR-SFTPConn-102 means SFTP authentication failed because of the SSH keys. Make sure the public key is in the server's authorized_keys on one line and that the .ssh permissions are correct.
- RVR-SFTPConn-103: problem with the private key fileRVR-SFTPConn-103 is an SFTP connection error tied to the private key file. Use a valid .pem key and upload it on a connection whose Credentials Type is Key File.
- RVR-SFTPConn-104: general SFTP connection problemRVR-SFTPConn-104 is a general connectivity problem with the SFTP server. Check allowlisting, the host and port, and the credentials, then test reachability from the network.
- RVR-SFTPStor-100: SFTP bad credentials or permissionsRVR-SFTPStor-100 means the SFTP server rejected the credentials or the user lacks permissions. Verify the credentials, allowlist the IPs and check the user's directory permissions.
Data Integration: Snowflake3
- RVR-SNF-001: Snowflake connection problemRVR-SNF-001 means Data Integration could not connect to Snowflake, usually because of wrong connection details or credentials without enough privileges. Verify the account, username, warehouse and role.
- RVR-SNF-002: Snowflake connection failureRVR-SNF-002 is a failure to connect to Snowflake from wrong credentials, missing permissions or account settings. Check the username and password first, including for unsupported characters in the password.
- RVR-SNFLGC-400: Snowflake process is missing valuesRVR-SNFLGC-400 means the Snowflake process lacks values it needs to continue. Check the Data Flow's required fields and column mapping, and look for nulls in key fields.
Data Integration: SSH1
Data Integration: SSH connection1
Data Integration: SSL connection1
Data Integration: Storage1
Data Integration: Stripe1
Microsoft Dynamics CRM connector1
More for Boomi work:Open Boomi jobsBoomi rates and salaries
The iPaaS Brief
Subscribe to The iPaaS Brief.
The iPaaS newsletter for the people who run integrations. From iPaaS Group.
Free. You finish on theipaasbrief.com and confirm by email.