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
    • Overview
    • API Credentials
    • Errors
    • Legacy & Deprecated APIs
  • Events API
    • Chat Markup
    • Rate Limits
    • Message Delivery
  • (Beta) Conversations API
  • Data API
    • GETList conversations
    • GETList interactions
    • GETList plugins calls
    • GETList Plugin Resources
    • GETList Users
  • Webhook Listeners
  • Content Gateway
    • Overview
    • Integration Strategies
    • Starter Code
    • Verifying Your Build
    • Connecting Your Gateway to Moveworks
    • Authentication
    • How Permissions Work
    • Common Pitfalls
    • Operational Guide
    • Errors
    • Supported MIME Types
  • Legacy Gateways
    • Authentication
    • Response Options
    • Field Types
    • Form Gateway Errors
DeveloperAcademyCommunityStatus
On this page
  • 400 FORM_OUT_OF_DATE
Legacy Gateways

Form Gateway Errors

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

In addition to the standard gateway errors, if you’re implementing a form gateway, you should implement the following error codes as well.

400 FORM_OUT_OF_DATE

Moveworks submitted a form which is no longer valid since it has been updated in the source system.

1{
2 "error": {
3 "code": "FORM_OUT_OF_DATE",
4 "message": "This form was last updated on 2022-10-20T07:00:00Z which is after the ingestion metadata date (2022-10-19T07:00:00Z)"
5 }
6}

If you surface this error code, Moveworks will gracefully handle it by linking your employees to the latest version of the form.