Overview
This article catalogs the errors you may encounter for the Moveworks integration in the iPaaS.com error logs (Dashboard / Integration Monitoring / Error Logs), grouped by mapping collection flow. Each entry carries a stable error code you can search for on this page. It covers three sources:
Integration errors raised by the iPaaS.com Moveworks integration itself.
Moveworks platform responses that the integration surfaces when Moveworks rejects a request. Because the Moveworks API failure is recorded by a single integration throw, every one of these carries the code MWKS-EXTN-1001, distinguished by the HTTP status shown in the message.
Mapping and formula validation errors raised by Dynamic Formula or filter logic in the mapping collection.
Some resolutions reference your Managed Integration Service Provider (MiSP) — the partner who configured and maintains your Moveworks integration, including its mappings, credentials, and Events Workspace configuration. Where a resolution goes beyond what you can adjust yourself, your MiSP is the first point of contact.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Moveworks Message Add From iPaaS.com
Error Collection
Moveworks Message Add From iPaaS.com
Message not sent
MWKS-EXTN-1003 - Could not Post Message To Moveworks
Description: The message transfer to Moveworks did not complete — the Moveworks send endpoint did not return a success response, so iPaaS.com could not confirm the message was created.
Resolution: Confirm the message provides a valid Event ID (an event that exists in your Moveworks Events Workspace) and at least one recipient email address. Review the related "Moveworks API call failed" entry for the underlying response from Moveworks. If the message data is correct and the failure persists, your MiSP can review the message mapping and the Moveworks Events Workspace configuration.
Moveworks API call failed
MWKS-EXTN-1001 - Error calling Moveworks CallWrapper.{action}: {details} (Http Code: {code})
Description: Moveworks returned a non-success HTTP status when iPaaS.com called its API. {action} identifies the operation, {details} is the response Moveworks returned, and {code} is the HTTP status code (see Moveworks Platform Responses below for what each code means).
Resolution: Read {details} for the specific reason and use the matching status code below. If the cause is unclear after checking the status code, your MiSP can review the request against Moveworks.
Moveworks request could not be completed
MWKS-EXTN-1002 - {details}
Description: The request to Moveworks could not be completed at the transport level (for example, the endpoint was unreachable). The error shows the underlying message; no HTTP status code is available.
Resolution: Confirm the API URL on the subscription is correct (https://api.moveworks.ai) and that Moveworks is reachable, then retry. If the endpoint is correct and the problem continues, your MiSP can confirm network reachability to Moveworks.
Invalid message identifier
MWKS-VALD-1001 - Invalid key value at {location}. MappingCollectionType = Message, ExpectedDataType = Integer, PKValue = {value}
Description: The identifier provided for the message is not in the expected format. This most commonly appears on a manual transfer when the value entered is not a valid iPaaS.com message internal ID.
Resolution: On the Manual Sync page, enter a valid iPaaS.com message internal ID (for example, 381443) in the IPAAS.COM field.
Moveworks Platform Responses
When Moveworks rejects the send request, the integration records it as the Moveworks API call failed error (MWKS-EXTN-1001) above, with the HTTP status shown as {code}. Per the Moveworks Events API reference, the send-message endpoint returns the responses below. Moveworks does not publish fixed message text for each, so read the {details} in the error for the specifics.
Bad Request (HTTP 400)
MWKS-EXTN-1001 - Http Code: 400 — Bad Request
Description: Moveworks could not process the request, typically because a required field is missing or malformed (for example, no recipients or no message body).
Resolution: Confirm the message maps a message body and at least one recipient email address, and that the request matches the Moveworks send-message requirements. If the mapping looks correct, your MiSP can review it.
Authentication Failed (HTTP 401)
MWKS-EXTN-1001 - Http Code: 401 — Unauthenticated (invalid or expired token)
Description: Moveworks rejected the request because the access token was missing, invalid, or expired.
Resolution: Re-check the Client ID and Client Secret on the subscription. If they are correct and the error persists, generate new OAuth 2.0 Client credentials in Moveworks Creator Studio and update the subscription; your MiSP can help if you do not manage the Moveworks OAuth client.
Not Authorized (HTTP 403)
MWKS-EXTN-1001 - Http Code: 403 — Unauthorized
Description: The credentials authenticated but do not have permission to send messages for the requested event.
Resolution: Confirm the Moveworks OAuth client has permission for the Events API and the target event. Your MiSP or Moveworks can grant the permissions if they are missing.
Event Not Found (HTTP 404)
MWKS-EXTN-1001 - Http Code: 404 — Event not found
Description: The Event ID does not exist in your Moveworks Events Workspace, or the credentials cannot access it.
Resolution: Verify the Event ID mapped to EventId exists in your Events Workspace. Replace the template's placeholder Event ID with your own before enabling the collection.
Rate Limit Exceeded (HTTP 429)
MWKS-EXTN-1001 - Http Code: 429 — Rate limit exceeded
Description: Too many requests were sent to Moveworks in a short period.
Resolution: Reduce the rate of message transfers and retry later. If you regularly hit this limit, contact Moveworks about your account's rate limits.
Mapping and Formula Validation
The template mapping collection does not include a mapping filter or any Dynamic Formula that raises a validation error, so there are no formula-level error messages in the default configuration. If a subscriber or their MiSP adds a Dynamic Formula or a mapping filter that throws a validation error (for example, to enforce a required field), that message will appear in the error log for this flow and should be added to this article.