-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 8.10-HF20, 9.3
-
Fix Version/s: 9.10
-
Component/s: Automation
-
Backlog priority:600
-
Sprint:nxfit 9.10.2
When, by mistake, the configuration references an operation that does not exist (not deployed on the server), getting the list of available operations fails. For example:
- Nuxeo Drive client cannot connect to the server (even if the missing operaiton is not related to Nuxeo Drive)
- Using
{server}
/nuxeo/site/automation/doc fails
Both fails with an error 500, server.log shows the error is linked to the missing operation (org.nuxeo.ecm.core.api.NuxeoException: org.nuxeo.ecm.automation.OperationCompoundException: No operation was bound on ID: Retention.CreateRule)
Typical example of mistake: Add to Studio registry an operation of a plugin that is not deployed on the server.
Instead of failing on everything, the platform should return the list of deployed operations, and display a warning (or an error, I don't know) about the missing operation(s)
- is duplicated by
-
NXP-17038 Automation Server should not crash if some bad operations are defined
- Open