Central Governance 1.1.3 Users Guide Save PDF Selected topic Selected topic and subtopics All content Flow status and deployment The flow status indicates the success of the last operation performed on the flow. The following table lists the possible flow statuses, deployment options, and their meanings. See also, Save and deploy a flow. Flow status Deploy options Comments Saved None The flow is incomplete; you cannot deploy it. In the Flow list, click the flow to open its Details view, and: Check for warning messages Complete the configuration as needed Saved, not deployed- Deploy The flow was never deployed, or was changed since the last deployment. When you click Deploy a check is performed to see if the deployment has an impact on another flow or legacy flow. If there is an impact, the deployment stops, the status becomes Saved, not Deployed, and is followed by a brief explanation: Conflict with another flow with the same IDF Conflict with legacy flows Click the link in the explanation message to check the Core Services logs for details. Force deploy Flow deployment is initiated without sending notifications if there is a conflict with other flows or with legacy flows, or if Transfer CFT requires a restart. See the examples scenarios in Troubleshoot flow deployment. Deployed None The flow configuration from Central Governance is already deployed on the products. Note When deploying a flow where Transfer CFT requires a restart (if you modify a SERVER type CFTSSL object ), the flow deploys in error and you are prompted to use “Force Deploy”. Deployed in error Deploy and Force deploy are enabled The last time the flow was deployed, it was not successful on some products. In the Flow List, click the flow name to check the flow details. Follow the link to the Deployment list page to check the status of each product in the flow. The last time the flow was deployed, it failed before starting deployment on some products. The flow deployment status details give information about the cause of the failure. See the examples scenarios in Troubleshoot flow deployment. Removed in error Deploy and Force deploy are disabled The last operation initiated on the flow was Remove, but it was not successful on all products. Deploying the flow is no longer an option. In Flow list, click the name of the flow to check the flow deployment status details. Follow the link to the Deployment list page and check the tooltip on the products with Removed in error status. To reinitialize removing the flow you can either go to the Flow list page select the flow and click the Remove button, or go to Deployments list page, select the product with status Removed in error and click the Retry button. Deploying None You cannot perform other operations on the flow until the deployment operation is complete. Removing None You cannot perform other operations on the flow until the remove operation is complete. Central Governance | Document Directory Related Links
Flow status and deployment The flow status indicates the success of the last operation performed on the flow. The following table lists the possible flow statuses, deployment options, and their meanings. See also, Save and deploy a flow. Flow status Deploy options Comments Saved None The flow is incomplete; you cannot deploy it. In the Flow list, click the flow to open its Details view, and: Check for warning messages Complete the configuration as needed Saved, not deployed- Deploy The flow was never deployed, or was changed since the last deployment. When you click Deploy a check is performed to see if the deployment has an impact on another flow or legacy flow. If there is an impact, the deployment stops, the status becomes Saved, not Deployed, and is followed by a brief explanation: Conflict with another flow with the same IDF Conflict with legacy flows Click the link in the explanation message to check the Core Services logs for details. Force deploy Flow deployment is initiated without sending notifications if there is a conflict with other flows or with legacy flows, or if Transfer CFT requires a restart. See the examples scenarios in Troubleshoot flow deployment. Deployed None The flow configuration from Central Governance is already deployed on the products. Note When deploying a flow where Transfer CFT requires a restart (if you modify a SERVER type CFTSSL object ), the flow deploys in error and you are prompted to use “Force Deploy”. Deployed in error Deploy and Force deploy are enabled The last time the flow was deployed, it was not successful on some products. In the Flow List, click the flow name to check the flow details. Follow the link to the Deployment list page to check the status of each product in the flow. The last time the flow was deployed, it failed before starting deployment on some products. The flow deployment status details give information about the cause of the failure. See the examples scenarios in Troubleshoot flow deployment. Removed in error Deploy and Force deploy are disabled The last operation initiated on the flow was Remove, but it was not successful on all products. Deploying the flow is no longer an option. In Flow list, click the name of the flow to check the flow deployment status details. Follow the link to the Deployment list page and check the tooltip on the products with Removed in error status. To reinitialize removing the flow you can either go to the Flow list page select the flow and click the Remove button, or go to Deployments list page, select the product with status Removed in error and click the Retry button. Deploying None You cannot perform other operations on the flow until the deployment operation is complete. Removing None You cannot perform other operations on the flow until the remove operation is complete. Central Governance | Document Directory