How to Fix Client Reports That Won’t Send?

Why am I seeing this?

When client reports generate successfully but never reach the recipient, the problem is almost always a broken connection to the custom email account you’re using to send them. If you’ve added your own Gmail or SMTP email in ManageWP’s 3rd Party Services settings (rather than using ManageWP’s default sender), that connection can break silently and reports will queue up unsent until it’s restored. The fix is to reconnect the email account. 

If you’re using ManageWP’s default email (noreply@managewp.com) and reports still aren’t arriving, this article doesn’t apply – please contact ManageWP support directly.

Key Takeaways

• Reports showing a warning icon (⚠️) instead of a sent icon (✉️) are generating fine. The issue is delivery, not generation.
• The most common cause is a broken connection to a custom email (Gmail or SMTP) added under 3rd Party Services.
• Gmail tokens get invalidated by Google without warning; SMTP credentials fail when your provider changes settings or your password resets.
• Once the email connection is restored, you can resend any failed reports manually.

What typically causes this?

If your reports show normal file sizes but a warning status, the generation succeeded and it’s the email delivery that failed.

The cause is almost always a broken custom email connection:

• Gmail (OAuth) accounts — Google invalidates OAuth tokens when you change your password, revoke ManageWP’s access, or exceed token limits. Workspace admin policies can also trigger revocation without any action on your part. Once invalid, reports keep generating but queue up unsent.
• SMTP email accounts — the connection fails when your password or app password resets, your provider changes its SMTP settings, or authentication requirements tighten. ManageWP still holds the old credentials, which no longer work.

How do I fix this error?

Step 1: Confirm the email connection is the problem

Before changing anything, verify that the issue is the email connection and not something else:

1. From your ManageWP dashboard, open Client Reports for the affected website.
2. Check the Status column. If recent reports show a warning icon (⚠️) but older reports show the sent icon (✉️), the reports are generating correctly and the problem is delivery alone.
3. Check which email address is configured to send these reports. If it’s a custom email you added under 3rd Party Services (not ManageWP’s default), the connection to that email is almost certainly the cause.

Step 2: Reconnect your email account

The fix is the same whether you’re using Gmail or an SMTP email: remove the connected account and add it back fresh.

1. Click your Profile icon in the upper right corner of the ManageWP dashboard.
2. Select Settings from the dropdown menu.
3. Navigate to the 3rd Party Services tab.
4. Find your email account in the list.
5. Hover over the email address. You’ll see Edit and Remove action buttons.
6. Click Remove to disconnect the email account.
7. Re-add the email account using the same connection flow you used originally.

For Gmail accounts, this means re-authenticating through Google’s OAuth flow. ManageWP will request permission to send on your behalf — approve it, and the fresh token replaces the expired one.

For SMTP accounts, you’ll re-enter your SMTP credentials (server, port, username, password). Before re-adding, confirm with your email provider that your credentials are still current — if your password changed or your provider now requires an app-specific password, use the updated credentials.

Step 3: Test the connection

After reconnecting, verify the email works before resending your queued reports:

For SMTP accounts: Go to Settings → 3rd Party Services → Email Accounts. Hover over the reconnected email address, click Edit, then click Test in the popup. If the test succeeds, your connection is working. If the test fails, double-check that your credentials are current and that your email provider hasn’t changed its SMTP port or authentication requirements.

For Gmail accounts: The Test button isn’t available for OAuth-connected accounts. Skip directly to Step 4 and send a test report instead. That confirms both the connection and the full delivery path.

Step 4: Resend the failed reports

1. Go to Client Reports for the affected website.
2. Find the reports that show the warning icon.
3. Send one report manually as a test. If it delivers successfully, your connection is restored.
4. Resend the remaining failed reports.

All future scheduled reports will now send automatically through the reconnected email.

What to keep in mind for next time?

A warning icon on generated reports means delivery failed, not generation. The cause is almost always a broken email connection, particularly for Gmail accounts where Google can invalidate tokens without any action on your part.

If your scheduled reports suddenly stop arriving across multiple sites at once, check your 3rd Party Services email connection first. It’s a 30-second diagnosis that saves chasing other explanations. For Gmail users specifically, changing your Google password or enabling 2-factor authentication will always break the token — plan to reconnect in ManageWP immediately after either of those changes.

Still stuck?

If reconnecting the email account and confirming the test didn’t resolve the issue, something specific to your email provider’s configuration may be blocking delivery. Contact ManageWP support with:

• The email address you’re using to send reports (Gmail or SMTP)
• Whether the Test function passed or failed (for SMTP accounts)
• The date reports stopped sending successfully
• Any recent changes to your email account (password reset, provider migration, new security policies)

That information lets the support team investigate without starting from scratch.

Frequently Asked Questions

Do I need to reconfigure my report schedules after reconnecting the email?

No. Your report schedules, templates, and recipient lists are all stored separately from the email connection. Reconnecting the email only refreshes the authentication — everything else stays exactly as you configured it.

Why did Google invalidate my token if I didn’t change anything?

Google revokes OAuth tokens for several reasons outside your control: security policy updates on their end, your account exceeding the per-client token limit (100 tokens, with the oldest silently dropped), Workspace admin policies, or the token going unused for six months. It’s not necessarily something you did. It’s a normal part of how Google manages third-party access to mail scopes.

Will my failed reports be sent automatically once I reconnect?

No. Reports that failed to send while the connection was broken won’t retry automatically. You’ll need to resend them manually from the Client Reports screen. Future scheduled reports will be sent automatically going forward.

Can I switch to ManageWP’s default email to avoid this issue?

Yes. If you don’t need reports to come from your own domain or branded address, switching to ManageWP’s default email (noreply@managewp.com ) removes the third-party dependency entirely. Reports will be sent from ManageWP’s servers without relying on an external email connection. You can change this in the report’s settings under the sender email option.

Does this affect reports across all my sites or just one?

All sites configured to send reports through the broken email address. Since the email connection is account-level (not per-site), all sites using that custom email will fail simultaneously. Once you reconnect, all of them resume working.