Skip to main content

​
Read the campaign report

Open Invitation campaigns, choose the campaign and check which sending account the run used. A connection status and an individual message outcome answer different questions. A later bounce can follow an earlier accepted or delivered event. Read the outcome and provider evidence together rather than adding every historical status as a separate recipient.

​
Retry deliberately

Connecting Resend does not restart a stopped campaign. Review the remaining recipients and the selected sending account before choosing a supported retry. Previously accepted invitations and uncertain deliveries retain their original provider record; changing accounts is not a way to resend them automatically. Consent, unsubscribe and duplicate protection remain enforced. When using your own Resend account, Perkstar does not buy an Emailable check or apply its shared address-quality verdicts and bounce-rate pauses. Your own Resend account can still suppress an address, exhaust a quota or reject a message under its policies. A Perkstar suspension or unrelated abuse restriction still applies.

​
Disconnect or replace the account

Open Integrations → Resend → Manage Resend and choose Disconnect Resend. This stops use of the saved sending key. It does not recall accepted emails. Sending remains unavailable until a replacement connection is explicitly activated; Perkstar does not silently switch these messages to its shared sender. You can also revoke the named Perkstar key and remove its webhook in Resend. Removing the webhook stops later delivery updates. Retain the relevant records while reconciling any pending or uncertain messages.

​
What to give support

Business account number, campaign name or reference, the approximate time, selected sender, visible error and the provider’s message ID if available. Do not include API keys, webhook secrets or a full customer list. See connection setup and the email sending terms.