Moveworks Error Messages
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. 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.
Mapping and formula validation errors raised by Dynamic Formula or filter logic in the mapping collection.
Supported Flows
Moveworks Message Add From iPaaS.com
Moveworks Message Add From iPaaS.com
Integration Errors
Message Not Sent
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, contact iPaaS.com Product Support.
Moveworks API Call Failed
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. Contact iPaaS.com Product Support if the cause is unclear.
Moveworks Request Could Not Be Completed
{message}
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 problem continues, contact iPaaS.com Product Support.
Invalid Message Identifier
Invalid key value at {location}. MappingCollectionType = Message, ExpectedDataType = {type}, 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 above, with the HTTP status shown as {code}. Per the Moveworks Events API reference, the send-message endpoint returns these responses. Moveworks does not publish fixed message text for each, so read the {details} in the error for the specifics.
Bad Request (HTTP 400)
HTTP 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.
Authentication Failed (HTTP 401)
HTTP 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.
Not Authorized (HTTP 403)
HTTP 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. Contact your MiSP or Moveworks if the permissions need to be granted.
Event Not Found (HTTP 404)
HTTP 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)
HTTP 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.