Resource Deletion and Its Effects
Deleting a resource removes that resource from its supported use. Review dependent projects and retained data before deletion.

Operation examples only; no deletion was performed. Confirm the target IDs and affected workflows before sending a destructive request. Deleting a source does not establish that previously generated answers or external copies are removed.
Before you begin
Permission to delete the resource and knowledge of its dependencies.
Key concepts
Archive
Removal from active organization views through the supported archive operation. It differs from permanent deletion and from unpublishing.
Unpublish
Withdraw the selected published availability of a project. Review active runs and trigger state separately.
Revocation
Withdrawal of a credential or access grant. Check dependent applications and separately issued links when access changes.
Retention
The period or policy for keeping a category of data. Deleting one resource is not a universal retention rule for all related systems.
Side effect
A change outside the returned answer, such as creating a record or sending email. Cancellation or release rollback does not undo a completed side effect.
Delete a resource
Identify projects, sources, or interfaces that reference the resource.
Use the resource’s delete control and read its confirmation.
Check dependent workflows and update references that are no longer valid.
The resource is removed and affected dependencies are identified.
Behavior and limitations
Deleting a project or connection does not undo external provider writes. Archive, unpublish, disconnect, and delete have different effects. Do not assume deletion is a complete retention or erasure operation across all exported files, histories, and external systems. Use the relevant data-management controls for each resource.
Related resources
Was this helpful?

