If users are fully into .fmu and have removed relevant fields in their global variables, the workflow WF_CREATE_CASE_METADATA is required in the ERT config to copy .fmu into scratch - otherwise the exports fails with "The global configuration was not provided..."
Previously when masterdata was located in the global variables this worked because there were other jobs in the ERT config that handled copying that file to scratch.
We should add some hint ala the .fmu folder does not exist, did you remember to include the WF_CREATE_CASE_METADATA workflow in your ert config?
If users are fully into
.fmuand have removed relevant fields in their global variables, the workflowWF_CREATE_CASE_METADATAis required in the ERT config to copy.fmuinto scratch - otherwise the exports fails with "The global configuration was not provided..."Previously when masterdata was located in the global variables this worked because there were other jobs in the ERT config that handled copying that file to scratch.
We should add some hint ala
the .fmu folder does not exist, did you remember to include the WF_CREATE_CASE_METADATA workflow in your ert config?