Actions let you trigger remote operations on an integration, such as asking an extractor to restart or reload its configuration. CDF tracks each action’s status as the extractor picks it up and completes it. You can create actions, list or retrieve their status, and cancel pending ones.
An action is a request for an integration to do something outside its normal task loop. The extractor receives pending actions in its next check-in response, runs them, and reports the outcome to CDF. This lets you manage extractors remotely without network access to the host where they run.
Triggering and tracking actions
You create an action against a specific integration, then poll or retrieve it to see whether it is pending, running, completed, or failed. If an action is no longer needed, you can cancel it before the extractor picks it up.
You can cancel an action only while it is pending, running, or cancel-pending. After the extractor reports completion, the outcome is final.
Key operations
- Create: Request a remote action on an integration.
- List and retrieve: Check the status of actions by integration or by ID.
- Cancel: Stop a pending or running action before it completes.
Actions give you remote control over an extractor’s behavior, complementing the passive monitoring that task history and error listing provide. 
