What is a one sentence summary of your feature request?
Improve the configuration deployment error messages to identify the specific parent and child objects involved in forced cascade deletion requirements.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
When a configuration import fails because --force-cascade-delete is required, the current error message only indicates the object types involved, for example:
The element: TaskInstance requires a forced cascade deletion for its parent: Task.
and
Please use the --force-cascade-delete to delete or archive items computed by the parent type: Task.
The message does not identify which Task(s) or TaskInstance(s) are causing the issue. As a result, administrators must manually compare configurations and investigate deployments to determine the root cause.
It would be very helpful if the deployment logs could include details such as:
The name and/or ID of the Task being deleted.
The number of impacted TaskInstances.
Optionally, the IDs or names of the affected TaskInstances.
The configuration file associated with the Task when applicable.
This would significantly reduce troubleshooting time and allow administrators to better assess the impact of using --force-cascade-delete before proceeding.
How do you currently solve the challenges you have by not having this feature?
Currently, we must manually investigate configuration differences, search for deleted or renamed Task definitions, review deployment packages, and sometimes query the database to identify the affected objects. This can be time-consuming and makes it difficult to understand the impact of the requested cascade deletion from the information available in the deployment logs alone.