Workato errors
Common Workato errors, grouped by component. Open one for the exact error text, its likely causes, the fix and the official documentation.
- Errors
- 78
- Components
- 19
- Verified
- 78
- Official docs
- docs.workato.com
78 errors in 19 groups
Agent Studio headless API3
- 401 auth_failed (headless API)A 401 with error_code auth_failed from the headless API means the token in the request was not accepted. Check, in this order, the token type, the data center host, whether the key was rotated, and the Authorization header format.
- 401 user_nonactive_or_missing (headless API)A 401 with error_code user_nonactive_or_missing means the X-IDP-User-Id header does not resolve to an active, allow-listed user. Confirm the user is active and belongs to an allow-listed user group.
- File too large (headless API file upload)The headless API rejects a file upload as "File too large" when the file is over the 20 MB maximum. Upload a single file of 20 MB or less as multipart/form-data.
API platform5
- 422 Processing error (API platform)A Workato API platform endpoint returns 422 Processing error when there is an issue with the API recipe and its job failed. Open the failed job, and check that the request matches the syntax the recipe expects.
- 500 Server error (API platform)A Workato API platform endpoint returns 500 Server error when the request parameters are missing or invalid for the API. Compare the request with the parameters the endpoint defines and send the missing or corrected values.
- access to this API has been disallowedA Workato API platform endpoint returns 401 with the message access to this API has been disallowed when there is a problem with the API token, the request configuration or the access policy. It is also returned when the request URL is incorrect or the endpoint is not active.
- concurrency limit exceeded / rate/quota limit exceededA Workato API platform endpoint returns 429 with concurrency limit exceeded or rate/quota limit exceeded when the client goes over a limit set by its access policy. Slow the client down, or raise the limit in the access policy.
- recipe execution takes too longA Workato API platform endpoint returns 504 with recipe execution takes too long when the API recipe's job does not respond within the endpoint's timeout. The default is 30 seconds and the maximum is 240 seconds, so make the recipe faster or raise the endpoint's timeout.
Connected app response6
- 400 Bad RequestA 400 Bad Request error in Workato means the external server could not process the request because it is malformed or invalid. Check field names, required values, record IDs and file sizes in the failing step, then reconnect the app.
- 401 UnauthorizedA 401 Unauthorized error in Workato means the external service rejected the authentication credentials sent with the request. Disconnect the app connection and reconnect it with valid, current credentials.
- 403 ForbiddenA 403 Forbidden error in Workato means the connection authenticated but is not authorized to access the resource or perform the action. Give the connected user the missing role, scope or permission in the app, then reconnect.
- 404 Not FoundA 404 Not Found error in Workato means the external service could not locate the resource your recipe tried to access. Check that the record ID is mapped correctly, belongs to the right object and app, and that the record still exists.
- 422 Unprocessable EntityA 422 Unprocessable Entity error in Workato means the external service received the request but could not process it because of a problem with the input data. Look for duplicate unique values, missing records, invalid reference IDs and empty required fields.
- 500 Internal Server ErrorA 500 Internal Server Error in Workato means the external service failed to process the request because of an internal problem on its side. Workato's documentation says you cannot resolve 500 errors directly in Workato, so check the external service and contact support.
Connector SDK CLI2
- Unable to publish custom adapter (workato push)workato push fails with "Can not publish adapter with code errors" when the connector code has syntax errors. The output lists each error with its line and position, so fix those and push again.
- VCR::Errors::UnhandledHTTPRequestErrorThis RSpec error means VCR could not match the connector's HTTP request to any recorded interaction. Record new interactions with VCR_RECORD_MODE=once, or relax the request matching in spec_helper.rb.
Database connectors1
Formulas1
HTTP connector4
- certificate verify failed (unable to get issuer certificate)This error means the certificate chain you supplied as custom CA certificates is incomplete or in the wrong order. List the server certificate, then the intermediates, then the root, separated by blank lines.
- err.http.response.client_error.too_many_requestsThe Workato error type err.http.response.client_error.too_many_requests means an HTTP connector request received a 429 response from the external API. Workato's documentation marks 429 as an error a retry can resolve, so retry the step after a delay.
- Microsoft Graph API connection disconnects after one hourAn HTTP connection to Microsoft Graph that disconnects after an hour is missing a refresh token, because the OAuth scope lacks offline_access. Add offline_access to the OAuth 2.0 scope field, save and reconnect.
- SSL_connect certificate verify failedThis error means Workato could not verify the target server's SSL certificate, because it is self-signed, the chain is incomplete, or the certificate is invalid for the domain. Upload the full certificate chain in the HTTP connection's custom CA certificate field.
On-prem agent11
- AgentNonRecoverableException: Error connecting to the gatewayThis on-prem agent error means the agent cannot complete a trusted HTTPS connection to the Workato gateway. The usual cause is SSL inspection, a proxy or a firewall intercepting the connection, so create an exception for the Workato gateways or configure the proxy in config.yml.
- Certificate not foundCertificate not found appears when a Workato on-prem agent is activated with the Windows Certificate Store selected and the agent cannot read the store. Store the key and certificate in the file system, or update the permissions on the certificate store.
- Failed to initialize MemoryUtil (Databricks JDBC)This error comes from the Databricks JDBC driver's use of Apache Arrow for data transfer. Add EnableArrow=0 to the JDBC URL.
- Failed to start SDK extension. 520 Connection FailedThis error means the SDK handshake between an on-prem extension and the Workato platform failed during startup. Build the extension with JDK 8 and make sure its post() URLs use the correct port.
- java.lang.OutOfMemoryError: Java heap space (on-prem agent)This error in the on-prem agent log means the agent does not have enough memory for a large job or payload. Raise the Java heap with the -Xmx option and restart the agent.
- Long query error: Missing files profileThis on-prem error means the On-prem files connection and the database connection in the recipe use different on-prem groups. Set both connections to use agents in the same on-prem group.
- No profile found (Kafka on-prem)"No profile found" means the on-prem agent cannot locate the Kafka profile named in the connection when the job runs. It is usually a config.yml mismatch, so check the kafka block, the profile name and the indentation.
- PKIX path building failedPKIX path building failed means the Workato on-prem agent cannot validate the SSL certificate chain of the host it is connecting to. Trust the missing certificates, or stop a proxy or SSL inspection tool from intercepting the agent's traffic to the Workato gateways.
- SFTP UnknownHostException through the on-prem agentThis error means the Hostname field of the Workato SFTP connection contains extra whitespace, so the on-prem agent cannot resolve the host. Remove the extra spaces from the Hostname and reconnect.
- Snowflake JDBC driver internal error (ArrowBuf.getDirectBuffer)This error appears on a select query in a custom SQL action against Snowflake through the on-prem agent. Add &JDBC_QUERY_RESULT_FORMAT=JSON to the connection URL.
- Unable to create directory [work] to use as the base directoryThis Workato on-prem agent startup error means the account running the agent does not have permission to create the work directory. Run the agent as an administrator, or give the service user full access to the install path.
On-prem files connector1
Oracle connector1
Parsers3
- CSV parsing errorThe Workato error type err.data_format.csv_parsing_error means CSV content could not be parsed because of a malformed structure or an invalid delimiter. Check the file for stray delimiters, such as commas inside values, and correct the source.
- JSON parsing errorThe Workato error type err.data_format.json_parsing_error means a JSON payload could not be parsed because of an invalid format or an unescaped character. Validate the source data and fix the document before it reaches the parser step.
- XML parsing errorThe Workato error type err.data_format.xml_parsing_error means an XML payload could not be parsed because of an invalid tag or a schema mismatch. Escape special characters in the XML and make sure the document matches the sample the step was set up with.
QuickBooks Online connector7
- 403 forbidden (QuickBooks Online)A 403 forbidden from the QuickBooks Online connector points to a connectivity issue with the QuickBooks Online app connection. Disconnect and reconnect the connection from the recipe's Connections tab.
- 784: unexpected token (QuickBooks Online)"784: unexpected token" means the QuickBooks API server is not responding properly, because of an outage or an intermittent issue. Check Intuit's status page and rerun the job when the API is back.
- app_already_purchasedapp_already_purchased appears when you create a QuickBooks Online connection and another user has already connected Workato to the same company account. QuickBooks allows one active Workato connection per company account, so have that user delete theirs or use a different company.
- Duplicate Name Exists Error (QuickBooks Online)The Duplicate Name Exists Error means the display name you are creating is already used by a customer, vendor or employee. Display names must be unique across those three, so add a prefix or suffix.
- Error 6210: Account period closed, cannot update through APIError 6210 means the transaction falls in a period that is closed in QuickBooks, so the API cannot update it. Remove the closing date in QuickBooks Online and rerun the job.
- Malformed Web Site Address format (2200)This QuickBooks error, code 2200, means a mapped website field does not start with http:// or https://. Make the value start with one of those prefixes.
- Object Not Found (QuickBooks Online)"Object Not Found" from QuickBooks Online means the recipe requested an object by an ID that does not exist in the account. Find the correct ID in the QuickBooks Online URL and fix the value or datapill.
Recipe job1
Salesforce connector4
- DUPLICATE_DEVELOPER_NAME on Monitor changes trigger restartDUPLICATE_DEVELOPER_NAME appears when a recipe with the Salesforce Monitor changes trigger ran once and then fails on restart. Try a fresh recipe or connection first, and if that fails delete the conflicting PlatformEventChannel in Salesforce.
- Salesforce connection disconnects repeatedly (Connection lost)A Salesforce connection that keeps showing "Connection lost" usually means Salesforce is not returning a refresh token. Grant the "Perform requests at any time" scope, then check the Refresh Token Policy and IP Relaxation settings.
- Salesforce connection failed: action failed due to server error"action failed due to server error" appears when you click Connect on a Salesforce connection and it fails. Check the Sandbox field against your domain, your custom OAuth settings, your IP allowlist and whether Salesforce has blocked the Workato app.
- Salesforce trigger failure: 414 URI Too LongA Salesforce trigger fails with 414 URI Too Long when it has too many fields selected, and the recipe stops processing jobs. Reduce the selected fields in the trigger configuration.
SAP connector7
- Cannot invoke IDocTypeBean.getSegMap() because "selected" is nullThis error means the agent tried to create a trigger before it finished retrieving metadata from SAP. Wait 90 seconds for the on-prem agent to retrieve the metadata, then try again.
- Classpath entry lib/sap-connector-X.X.X.jar not found, skippedThis message appears on macOS when sap-connector-X.X.X.jar was moved into lib_ext. Keep that file in its default location.
- java.lang.NoClassDefFoundError: com/sap/conn/idoc/jco/JCoIDocThis error means the SAP Java IDoc Library is missing from the agent. Download SAP JIDocLib and add sapidoc3.jar to the lib_ext folder.
- java.lang.NoClassDefFoundError: com/sap/conn/jco/JCoExceptionThis error means the SAP Java Connector (JCo) library is missing or is not on the agent's classpath. Add the JCo files to lib_ext and make sure config.yml lists lib_ext in the classpath.
- java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.pathThis error means the agent's SAP Java Connector package does not match the host operating system. Download and install the JCo version for the agent's OS.
- JCo initialization failed with java.lang.UnsatisfiedLinkErrorThis error stops the on-prem agent from starting on Windows because JCo 3.1 needs the Microsoft Visual C++ runtime libraries. Install the latest Microsoft Visual C++ 2015-2022 Redistributable Package on the agent server.
- Registration of tp from host not allowedThis SAP connection error may indicate a problem in the SAP gateway's reginfo or secinfo files. Follow SAP note 1850230: check the files and the gw/* parameters, and confirm the agent host can reach the SAP gateway host.
SAP Data Agent13
- General SAP error RSODP_ODATA/012RSODP_ODATA/012 means SAP hit a problem while extracting a data package for the pipeline. Run the pipeline again.
- No DTP found for the entered OHDThis SAP BW error means the Open Hub Destination exists but no Data Transfer Process is created or assigned to populate it. Create and assign a single DTP and execute it before starting the extraction.
- No service found for namespace, name, version 0001This error means the service name or URL configured for the data source in /WKTO/ODP_CONFIG is wrong. Look up the External Service Name in /IWFND/MAINT_SERVICE and update the configuration.
- Not authorized to access table/viewThis SAP Table Reader error means the SAP technical user running the extraction lacks authorization for the table or view. Capture the missing authorization with SU53 and assign the SAP Table Reader role.
- OHD having multiple DTP is not supportedThis SAP BW error means more than one Data Transfer Process populates the Open Hub Destination, and only single-DTP OHDs are supported. Make sure one DTP populates the OHD, or create a new OHD linked to a single DTP.
- Pipeline details not found"Pipeline details not found" from the SAP Table Reader means SAP has no runtime details for the pipeline ID. Verify the pipeline ID and make sure cleanup is not running too early.
- Primary key has been changed on the source's sideThis data pipeline error means the key fields of the SAP data source changed. Open the pipeline's Objects tab and click Re-sync for the object.
- SAP ODP connection timeout (General SAP error UNKNOWN, 500)Either message means the SAP server closed the connection before returning an extraction response, because the ICM timeout is too short for the configured page size. Increase the timeout first, then reduce the page size if it still fails.
- SAP ODP2 data source is now driven by another subscriptionThis error means the pipeline's subscription was terminated manually in SAP and another pipeline then started incremental sync on the same data source. Delete this pipeline, decide which pipeline to keep, and recreate if needed.
- SAP ODP2 data source subscribed for a fresh initial load, but its DeltaLinks history is not emptyThis error means an initial load started while delta entries still exist in SAP, usually just after an earlier pipeline's subscription was deleted. Wait about 5 minutes and run again, and if it persists delete the orphaned subscription.
- SAP ODP2 subscription has no delta entries while local state carries a deltatokenThis error means the subscription for this pipeline was terminated manually in SAP. Delete the pipeline and create a new one for the same data source, which starts with an initial load.
- SAP ODP2 subscription is already held by another pipelineThis error means incremental sync was started for an ODP service that another pipeline already uses for incremental sync. Each ODP service supports incremental sync in one pipeline only, so create a new ODP service or release the existing subscription.
- Table/View Not available while checking authorizationThis SAP BW Open Hub error means the technical user lacks authorization to the table or view. Capture the missing authorization with SU53 and assign the /WKTO/BWOHD role.
SFTP connector4
- closed stream on Upload file to SFTP serverA "closed stream" error on the Upload file to SFTP server action points to an interrupted transfer, often with a small transfer buffer on a large upload. Increase the transfer buffer size in the SFTP connection settings.
- No such file on the New/updated CSV file in directory triggerWhen the New/updated CSV file in directory trigger keeps failing with "No such file" even after a restart, its cursor points at a file the server deleted or moved. Set Ignore Missing Files? to true.
- password must not be longer than 1024 bytesThis SFTP connection error means the Private key passphrase field holds more than 1024 characters, often because it auto-filled with the private key itself. Create a new connection and leave the passphrase blank or type it in manually.
- SFTP error 2 : no such file"SFTP error 2 : no such file" on the New/updated file in directory trigger means the file was gone or unreadable when Workato tried to download it. Keep files in the monitored directory until they are downloaded and make sure uploads are complete.
SQL Collection by Workato1
Webhooks3
- 400 Bad Request on webhook eventsA webhook event sent to Workato gets a 400 Bad Request when its payload does not match the Webhook type configured on the trigger, or is not UTF-8 compatible. Match the Webhook type to the payload, or use Raw Binary Data for non-UTF-8 content.
- 429 Too Many Requests (webhook gateway)Workato's webhook gateway returns 429 Too Many Requests when incoming webhook events exceed both the steady rate and the burst allowance. The sender should retry the webhooks until they are accepted, using the Retry-After header.
- Error generating schema for responseError generating schema for response appears in Workato's webhook setup when the Content-Type header of the webhook does not match its payload. Have the sender fix the format, or skip the guided setup and define the payload schema manually.
More for Workato work:Open Workato jobsWorkato rates and salariesHire a senior Workato developer
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.