Validation and error messages

This table lists the status of the supported cycle period and scenarios for which the macro command can be executed:

Cycle Period Status	Scenario Status	Can Execute?	Validation Message
Pending	N/A	No	Cannot run macro {0} because Cycle Period has status "Pending".
Running	Any	Yes	N/A
Completed	Any	Yes	N/A
Aborted	Any	Yes	N/A
Paused	Any	Yes	N/A
Archived	Any	No	Cannot run macro {0} because Cycle Period has status "Archived"

This table lists the error messages displayed for various validation failures:

Validation Condition	Error Message
Check that the passed interface service is valid.	Interface Service "{0}" cannot be found
If the Direction does not match the Interface Direction of the selected Interface Service, the macro is not executed.	Direction parameter {0} does not match the direction of the selected Interface Service "{1}".
When direction = Import, the cycle period must be set to ‘Available’ with a WIP scenario.	Cannot execute RunInterfaceService with direction of import for a cycle period with status "{0}".
If the calendar level is not higher or equal to the Calendar level for storing scenario values, a warning message is displayed, and the Import process is aborted.	Calendar Level {0} is below the Calendar level {1} for storing scenario values.
RunInterfaceService in cycle period context must be from a cycle period with Running, Paused, Completed, Aborted status.	Cannot execute RunInterfaceService for a cycle period with status {0}.
If the selected Interface Service data entity is not applicable to the current macro context, the macro is not executed, that is, RunInterfaceService can only run interfaces of data entity = calendar in a cycle period context.	Interface Service {0} does not match the data entity required for a cycle period macro.
When executing RunInterfaceService in a cycle period context, the selected interface service must refer to a calendar that matches the calendar of the current cycle period. Else the macro is not executed.	Calendar referenced in Interface Service {0} does not match the calendar of the current cycle period
When executing RunInterfaceService for export, check that the horizon level, if specified, is valid.	Horizon Level {0} cannot be found.
When executing RunInterfaceService for export, check that the horizon level, if specified, is at or above Calendar Level to store plans (if the Telescopic option is not enabled).	Horizon Level {0} is below the Calendar level {1} for storing scenario values
Check that Data Source is of the same type defined in the Interface service.	Data Source {0} type doesn't match the data source type in Interface Service "{1}".