404 NOT_FOUND and, in some cases, 403 Forbidden errors.404 NOT_FOUND "Failed to validate form source due to: "; nested exception is org.springframework.web.server.ResponseStatusException: 404 NOT_FOUND https://vra-FQDN/vro/forms/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/context?projectId=. An example of the 403 Forbidden response is: json { "error": "Forbidden", "message": null, "path": "/vro/forms/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/context", "requestId": "xxxx-xxxx", "status": 403, "timestamp": 1724386720566 }When a Day-2 action call is initiated from the machine's DataGrid (i.e., outside the direct deployment view), the deployment ID parameter provided is empty. This prevents the system from correctly retrieving the associated actions, leading to the 404 NOT_FOUND error.
This issue is resolved in patch 1 and above for Aria Automation 8.18.1
Aria Automation 8.18.1 Patch 1 instructions available in KB 385294.
Aria Automation 8.18.1 Patch 2 instructions available in KB 394224
Aria Automation 8.18.1 Patch 3 instructions available in KB 403690
Workaround: The workaround is to run custom Day-2 actions directly from inside the deployment view. This means users should navigate to Service Broker -> Deployments in the UI and initiate the action from there, rather than from other views like the machine's DataGrid.