Overview

These actions operate within an Asynchronous Command Processing (ACP) model that is backed by a queuing system. When an action is invoked through the API, the successful outcome of the request is the reliable placement of a work item into the appropriate queue. The ACP status codes and response messages confirm that the event was accepted and queued for processing, not that the underlying operation has completed at runtime. The actual execution occurs later within the Origami processing pipeline (usually within a few seconds to a few minutes depending on activity and queue traffic). This supports resilient, scalable, and responsive performance even under heavy load.