Description:

Forge Automation Actions implemented using the endpoint property (backed by Forge Remote) do not support the documented error 

{ errors: [{ message }] } 

response contract.

According to the Forge documentation, an automation action can communicate errors by returning:
 

{
  "errors": [
    {
      "message": "A user-facing error message"
    }
  ]
} 

This works correctly for actions implemented via Forge function. However, for actions implemented via endpoint (Forge Remote), this contract is not honoured — custom error messages are never surfaced in the Jira Automation audit log.

Behaviour by HTTP Status Code

Impact

Forge Remote-backed Automation Actions cannot communicate meaningful validation or domain errors to users. This makes it impossible for users to understand why an action failed or how to correct their rule configuration.