[ML] Anomaly Detection: Custom rule may prevent job cloning

[walterra]

Custom rules may trigger errors in the advanced wizard when cloning a job. Failing job validation may block a user from cloning the job.

On the first step of the job wizard, model memory estimation may fail. This is just a warning message and will not block the user from moving on with the wizard.

However, the validation step may fail completely and block the user from moving on:

The errors relate to parsing errors with custom rules:

{"statusCode":400,"error":"Bad Request","message":"[request body.analysisConfig.detectors.0.custom_rules.0.conditions]: expected value of type [array] but got [undefined]"}

Workaround

On the second wizard step "Pick fields", use the "Edit JSON" button to open the editing flyout and remove the custom_rules section:

Save the change and return to the wizard. The removed custom rules should allow you to pass the validation step.

Unfortunately you may hit a problem where the JSON editor's save button may stay grayed out even if you changed the configuration. I could work around that by also removing e.g. the custom URLs section.

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[walterra]

Note: This issue wasn't reproducable on latest master for me, further investigation needs to be done to identify affected versions.

[jgowdyelastic]

Which version was this seen in?
This should have been fixed in 7.9.0 by #74676

[walterra]

Thanks for the link, this was reported on 7.8.1, so closing the issue.

[TomonoriSoejima]

I just also confirmed 7.9.0 has no issue!