The "Rejected Information" project focuses on improving the delivery of information to customers by implementing a system that allows storing events and summaries, which have not been received by our customers, in specific buckets so they can request and retrieve any pending documents proactively. In this way, our aim with the project is to mitigate information loss and ensure effective data delivery to customers. The project also includes implementing a retry process before storing the documents in the bucket, which consists of notifications to the customer to make them aware of pending events and webhooks awaiting acceptance.
The operation of the "Rejected Information" project can be described in the following steps:
- Initial document sending: When attempting to send events and summaries to the customer via webhook, a retry process is initiated if the document is not received correctly by the customer in the first attempts.
- Retry process: A retry flow is established, including three delivery attempts of the document to the customer after 2 hours, 24 hours, and 48 hours. If the customer does not receive the document after these retries, the document is moved to the storage bucket of the corresponding environment (sandbox or production).
- Storage in buckets: Events and summaries that could not be delivered to the customer are stored in designated buckets for each environment, allowing the customer to request the resend of the stored information if necessary. This information will be available for proactive customer requests for 3 days for the sandbox bucket and 10 days for the production bucket.
- Customer notifications: Notifications will be sent via webhook to inform customers about the existence of pending events and summaries awaiting acceptance in the buckets.
- Preference management: Customers have the ability to manage their notification preferences, therefore, they can request not to receive these retry notifications. However, unreceived events and summaries will still be stored in the bucket under the same time rules.
This project ensures that events and summaries not sent to customers are securely stored in production or sandbox buckets, allowing customers to request pending information in case of initial delivery failures. Additionally, notification mechanisms are established to ensure effective data delivery to customers.
Frequent Questions
What is the Reject Information project about?
The goal of Resend Reject Information is to improve the delivery of information to customers by ensuring they receive the maximum amount of data about their users, so we aim to maintain communication despite the lack of response from the customer's side.
How is information loss prevented?
The objective is to establish a system where information sent to customers is stored in buckets to allow them to request and retrieve any pending documents, thus mitigating the risk of information loss.
How long are documents not received by the client kept??
Events and summaries not received by customers will be stored in their respective buckets within their environment. For the production bucket, events and summaries will be stored for 10 days, and for the Sandbox bucket, they will be stored for 3 days. After this period, they will be deleted from the buckets, but the customer can still request the events and summaries. This has to be requested directly to the account manager and will incur an additional cost.
What is the process for handling resend attempts before storing documents in the bucket?
Before storing documents in the specific bucket of the environment, a retry process is initiated, which involves two attempts to send the document to the customer at intervals of 2 hours and 24 hours after the first notification. If the customer does not receive the document after the retries, then it is moved to the respective bucket.
How does the project ensure effective communication with customers regarding pending documents?
The system will use webhooks to notify customers when events and summaries are queued for delivery and are not successfully received. Customers can also request the resend of pending documents through the designated endpoint.
How does the project differentiate between sandbox and production environments in terms of document delivery?
Separate buckets and endpoints will be established for sandbox and production environments to ensure different handling of documents for each environment.
How can I subscribe to this parallel webhook notifications?
You will need to send us a URL where you want the notifications to be sent; this process will be manual for the time being.