For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
ReferenceGuides
ReferenceGuides
  • Agent Studio
    • Overview
    • Quickstart Guides
    • Core Concepts
    • Conversation Process
    • Actions
      • LLM Actions
      • Built-in Actions
      • HTTP Actions
        • HTTP Action Data Bank
        • Event streaming (SSE) and XML responses
        • HTTP Action Files
        • HTTP Action Troubleshooting
        • Data Mapper in HTTP Actions
        • HTTP -> LDAP Actions
        • Optional Query Parameters in HTTP Actions
      • Script Actions
      • Compound Actions
    • Connectors
    • System Triggers
    • Agent Architect
    • Cookbooks
    • Development and Testing
    • AI Agent Marketplace
    • Developer Tools
  • Agentic AI
    • LLM Fundamentals
    • The Agentic Reasoning Engine
    • Memory Constructs
    • Conversational Context
    • Guardrails
    • Grounding and Hallucinations
    • Continuous Learning
    • LLMs & SLMs
    • Steerability Tools
    • Multilingual Support
  • Core Platform
    • User Identity
    • Moveworks Agent (On-Prem)
    • Approvals Engine
    • Entity Catalog
    • Moveworks Data Objects
    • Security Information and Event Management (SIEM) Logs Overview
DeveloperAcademyCommunityStatus
On this page
  • Error Code: 10107
  • Error Code: 10111
  • Missing Variables
  • Incorrect Usage of Brackets
  • Error Code: 10118
  • Error Code: 10113
  • Query Parameter Encoding Breaks Special Characters
Agent StudioActionsHTTP Actions

HTTP Action Troubleshooting

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Data Mapper in HTTP Actions

Build complex JSON payloads directly in the HTTP Action body editor using Data Mapper syntax.
Next
Built with

Error Code: 10107

️ Authorization failed

This error message is typically surfaced when the connector uses a 2-step authentication method and needs make a /token request first. In these cases, the /token request failed.

For example, connectors that use OAuth 2.0 Client Credentials, make a request to a /token endpoint in order to get an access_token. We then use that access_token to make the primary request.

We recommend validating your HTTP action in Postman or another API testing tool first. Once you are confident your API works, then you can recreate it in Moveworks using the cURL import option. Make sure that all headers, query params, and body are properly set.

Error Code: 10111

️ Failed to construct request. Please make sure that all variables denoted by {{{}}} have corresponding example values

There are a few reasons why your request may fail to be constructed properly.

Missing Variables

Your error message may have more details like

missing variable \”okta\”

or some other variable. This means that variable was never defined:

Incorrect Usage of Brackets

Moveworks uses the Mustache protocol for body templating. This means…

  • All strings should be escaped in triple brackets & inside quotes (e.g. "{{{my_string_value}}}")
    • Note: triple brackets disable HTML escaping, but if you want to leave HTML escaping on, then provide double brackets
  • All numbers or booleans should be provided in double brackets (e.g. {{number}})

Error Code: 10118

️ Invalid host name

Check if the base URL in your connector starts with https:// or http://

️ Unable to resolve host name

The hostname may not exist. Double check your base URL is configured properly

The hostname may be private. You can check if a DNS Record is found by copy & pasting your base URL on mxtoolbox.com

Error Code: 10113

️ Failed to make API request

This error message forwards the response of the original API Request.

We recommend validating your HTTP action in Postman or another API testing tool first. Once you are confident your API works, then you can recreate it in Moveworks using the cURL import option. Make sure that all headers, query params, and body are properly set.

Query Parameter Encoding Breaks Special Characters

Plus signs (+) and other special characters are altered in query parameters

When a slot value is passed into a query parameter, the Action query parameter generation may URL-decode and then re-encode the value. This can cause + characters to be converted to spaces, corrupting the original value.

This commonly affects any slot value that contains a + character — for example, ISO 8601 timestamps with timezone offsets (2024-01-15T10:30:00+05:00), Base64-encoded strings, or any user-provided input that includes +.

Workaround: Use $REPLACE in DSL to pre-escape the + character before it reaches query parameter encoding:

1my_param: $REPLACE(data.my_slot_value, '[+]', '%2B')

$REPLACE uses regex, so the + must be wrapped in a character class [+] to be treated as a literal character rather than a regex quantifier.