WFM Evaluate API 422: 'Invalid Evaluation Form ID' on Multi-Org Premium App Integration

Genesys Cloud WFM
1 
{
 "message": "The evaluation form ID provided is invalid or does not exist in the specified organization.",
 "code": "invalid_evaluation_form_id",
 "status": 422
}

Our AppFoundry premium application, which operates across multiple Genesys Cloud organizations via multi-org OAuth, is currently failing to sync evaluation results from our external Quality Management system. The integration uses the POST /api/v2/wfm/evaluate/evaluations endpoint to push completed evaluations into Genesys Cloud. While the initial authentication and token refresh mechanisms are functioning correctly, we are encountering a persistent 422 Unprocessable Entity error specifically during the evaluation submission phase.

The issue appears to be isolated to specific evaluation forms that have been recently modified in the Genesys Cloud UI. The application successfully retrieves the list of available evaluation forms using the GET /api/v2/wfm/evaluate/forms endpoint, and the IDs match exactly what is being passed in the submission payload. However, the submission fails with the error above.

Steps to reproduce the issue:

  1. Authenticate the AppFoundry application using the multi-org OAuth flow, obtaining a valid access token for the target organization.
  2. Retrieve the list of evaluation forms using GET /api/v2/wfm/evaluate/forms and identify a form that has been updated within the last 24 hours.
  3. Construct the evaluation payload including the formId, agentId, interactionId, and the required scorecard object with all mandatory fields populated.
  4. Submit the payload via POST /api/v2/wfm/evaluate/evaluations.
  5. Observe the 422 error response indicating an invalid form ID.

We have verified that the form is published and active in the WFM Quality Management module. Additionally, manual submissions of the same evaluation data through the Genesys Cloud UI succeed without issue. This suggests the problem lies within the API validation logic or a caching discrepancy between the form retrieval and evaluation submission endpoints.

Has anyone encountered similar behavior with recently updated evaluation forms? We are considering implementing a retry mechanism with a longer delay, but we would prefer to understand if there is a known latency in form ID propagation or a specific requirement for form versions that we might be missing. The application is built on the latest Genesys Cloud SDK for Node.js (version 2.11.0).