A failed or interrupted request does not always tell you whether a pack was delivered. Check the existing send before starting a new one.

Keep the current workflow open. It retains your current edits while you check the result.

Select Check send status, then follow the result:

Retry submitted copy retries the same submitted copy. Edits made after that submission are not added to the retry.

Resolve send determines whether the earlier attempt sent a pack. Follow its confirmed result: view a sent copy, or review and send again only after the app confirms that nothing was sent. The retry controls may disappear once the attempt is resolved.

Retrying and resolving are alternatives for an uncertain attempt, not steps that must both be performed. Wait for a confirmed result before starting a different send.

If the result cannot be resolved, contact human support. Do not start repeated new sends to find out whether one worked.

If the app shows pending sends, select Resolve pending send before repeating a delivery. It can check the earlier submitted attempt without restoring an unsent personalized draft.

A submitted-attempt recovery record is different from saved personalization. Unsent personalized content does not survive a new session.

The app checks the current assignment again at send time. An expired subscription or changed assignment can prevent a new send.

Ask human support to review a specific client's eligibility. Access to an old sent copy does not make the client eligible for another delivery.

For an unresolved send, provide your role, the affected step, approximate time and timezone, and the exact status or error. Add a non-sensitive pack name or reference if available. Avoid including private client content.

Ask for a human immediately for account access, a specific eligibility decision, privacy/security concerns or suspected data loss. Fin can explain the documented steps; it cannot claim to send, cancel, delete or repair a pack on your behalf.