We fixed an issue where introducing a delay object in the request to the cancel endpoint resulted in a 404 response. Previously, the absence of a database table for requests meant cancellations relied on matching message IDs. Since no messages existed, there was nothing to cancel, causing the endpoint to return an error. This problem has now been resolved, ensuring proper functionality of the [cancel endpoint](https://www.courier.com/docs/rest/reference/messages/cancel).