Exclude analysis output attributes when the analysis is suspended
When the PI Analysis service determines an Analysis should be Suspended, it should also set any output Attributes to be Excluded. As the Analysis is Suspended, it will not output any results and if it has always been Suspended, the output Tags will never get created. Excluding the output Attributes will keep the Element looking clean and also allow dependent Analyses to go into a Suspended state instead of throwing an error when they can't find the Tags. Similarly it will prevent other applications (OSIsoft and third parties) from querying the Attributes and also throwing errors, causing performance issues.
Automatically suspended Analyses when the inputs are excluded was an extremely useful feature and has made supporting and maintaining an AF database easier. Automatically excluding the output attributes is a natural progression of this feature and will make AF database even more easier to maintain.
How long do you expect these analyses to be suspended? The original implementation of a "suspended" state is based on the assumption that it's a somewhat transient condition and at some point in time, you would "correct" the suspended analyses to run appropriately. Please describe your use case.
Temirbek Yermagambetov commented
Good feature. In our company we faced the same issue, when you create an analysis, which has input attribute with a properties excluded and it creates output tag. It is weird and cause lots of performance issues. At the same time, because of the analysis is suspended output tag always shows 'Calc failed'.