Skip to main content

Overview

The delete method allows you to permanently remove an experiment from your account. This action is irreversible and will delete all associated data including results and configurations.

Method Signature

Synchronous

Asynchronous

Parameters

Returns

Returns a dictionary confirming the deletion with details about the deleted experiment.

Examples

Basic Deletion

Safe Deletion with Confirmation

Check Status Before Deletion

Asynchronous Deletion

Batch Deletion

Conditional Deletion

Backup Before Deletion

Asynchronous Batch Deletion

Delete with Metadata Check

Deletion with Audit Log

Safe Deletion Function

Error Handling

Safety Considerations

  • Irreversible Action: Deletion permanently removes all experiment data
  • Running Experiments: Some systems may prevent deletion of running experiments
  • Data Loss: All results, configurations, and metadata will be lost
  • Dependencies: Check for any dependent systems or reports before deletion
  • Backup: Consider backing up important experiment data before deletion

Best Practices

  • Always confirm deletion for important experiments
  • Check experiment status before deletion
  • Backup experiment data if results are valuable
  • Use batch deletion carefully with proper error handling
  • Maintain audit logs for compliance and tracking
  • Consider “soft deletion” (marking as deleted) for critical experiments

Alternative Approaches

Soft Deletion

Archiving

Common Use Cases

  • Cleaning up old draft experiments
  • Removing failed or invalid experiments
  • Batch deletion of temporary experiments
  • Removing experiments after data export
  • Cleanup during account migration
  • Removing experiments with sensitive data