Skip to main content
Most issues in Aflux fall into a handful of predictable categories. Work through the relevant section below to resolve your problem quickly. If none of the steps here solve your issue, reach out to us at support@aflux.io and include as much detail as possible about what you were doing and the error message you saw.

​
Storage & Integrations

This is almost always caused by OAuth permissions being denied or only partially granted during the connection flow.Steps to resolve:
  1. Go to Settings → Integrations and disconnect Google Drive if it is shown as partially connected.
  2. Click Connect Google Drive again and complete the full OAuth flow. Make sure to grant all requested permissions — Aflux requires read/write access to function correctly.
  3. If the problem persists, sign out of your Google account in your browser, sign back in, and retry the connection.
  4. Try the flow in a private/incognito browser window to rule out cached credentials or conflicting extensions.
If you manage multiple Google accounts, confirm you are authorising the correct account during the OAuth flow.
If your Drive is connected but files aren’t showing up in the Aflux file browser:
  1. Refresh the file browser — click the refresh icon or reload the page.
  2. Check Google Drive Trash — files in the Trash are not accessible to Aflux. Restore the file in Drive and try again.
  3. Verify the connected account — go to Settings → Integrations and confirm the displayed Google account email matches the account that owns the files.
  4. For shared Drive files, make sure your account has at least Viewer permissions on the file in Google Drive itself.
This error can have two distinct sources:
  • Aflux internal storage quota — your plan’s internal storage limit has been reached. Free up space by deleting files stored directly in Aflux, or upgrade your plan for a higher limit.
  • Google Drive quota — if you are using Google Drive as your storage backend, the quota is governed by your Google account, not by Aflux. Manage your Drive storage at drive.google.com or upgrade your Google storage plan.
Using bring-your-own storage (Google Drive) is the best way to avoid Aflux internal storage limits entirely — your Drive quota is managed independently.

​
Bulk Email

If your campaign is stuck or fails to send, check the following:
  1. Contacts list — confirm your selected contacts list is not empty. A campaign cannot send without at least one valid recipient.
  2. Monthly email limit — check your remaining send quota in Settings → Billing. Free accounts are limited to 100 emails/month. If you’ve hit the limit, the campaign will be queued until the next billing cycle or you upgrade.
  3. SPF/DKIM configuration — if you are sending from a custom domain, verify that SPF and DKIM DNS records are correctly configured for that domain. Campaigns from unverified domains may be blocked. Check your DNS provider’s documentation to add SPF (v=spf1 include:mail.aflux.io ~all) and DKIM records for your domain.
A high bounce rate signals that a portion of your contact list contains invalid or unreachable addresses.
  1. Open the campaign report and download the Bounce Report to identify affected addresses.
  2. Remove hard-bounced addresses from your contact list — continuing to send to them will damage your sender reputation.
  3. Use a list-cleaning tool or double opt-in flow to validate addresses before adding them to future campaigns.
Repeatedly sending to hard-bounced addresses can result in your sending domain being flagged by mail providers, which affects deliverability for your entire contact base.
Spam classification is determined by receiving mail servers based on several factors. To improve deliverability:
  1. Set SPF, DKIM, and DMARC records on your sending domain. All three records working together significantly improve inbox placement.
  2. Review your subject line — avoid all-caps, excessive punctuation (e.g. !!!), and words commonly flagged as spam (e.g. “FREE”, “ACT NOW”).
  3. Warm up a new domain — if you recently set up a new sending domain, start with small send volumes and increase gradually over several weeks.
  4. Ask engaged contacts to mark your emails as “Not Spam” to build positive sender signals.

​
E-Signature

  1. Ask the signer to check their spam or junk folder — signature request emails are sometimes filtered, especially for first-time senders.
  2. Resend the request from E-Signature → select the document → Resend. The signer will receive a fresh notification.
  3. Verify the email address — open the document in E-Signature and confirm the signer’s email address was entered correctly. A single typo means the email was delivered to a different address.
If your sender domain is not SPF/DKIM verified, signature request emails are more likely to land in spam. Ensure SPF and DKIM records are configured for your sending domain to improve deliverability.
Signature requests have an expiration date set at the time of creation. Once expired, the signing link becomes inactive.To resolve this, resend the request with a new expiration date. Setting a custom expiration date is a Pro and above feature. On the Free plan, the default expiration window applies and cannot be extended — upgrade to Pro to gain full control over expiration dates.
Aflux E-Signature only accepts PDF files. Ensure the document meets these requirements before uploading:
  • Format: PDF (.pdf) only — Word, Excel, and image files are not supported directly; convert them to PDF first.
  • File size: Free plan documents must be under 10 MB. Pro and above have no file size limit.
  • PDF permissions: Some PDFs are protected with owner passwords that prevent modification. Remove any restrictions before uploading.
The audit trail is generated automatically once all required signers have completed their signatures. If it is not yet available:
  1. Wait a few minutes — audit trail generation runs as a background process and may take up to 5 minutes after the final signature.
  2. Refresh the document view in E-Signature to check whether the trail has appeared.
  3. If the audit trail is still missing after 15 minutes, contact support@aflux.io with the document name and the date of completion.

​
QR Codes

Scanning failures are almost always a print or resolution issue rather than a code configuration problem.
  1. Download a higher-resolution version — from QR Codes → select the code → Download and choose SVG format. SVG is vector-based and scales to any print size without losing quality.
  2. Check for physical damage — a torn, creased, or partially obscured code may not scan reliably. Reprint if necessary.
  3. Test with multiple scanner apps — different devices and apps have varying scanning capabilities. Try the native camera app and a dedicated QR scanner.
  4. Ensure there is adequate quiet zone (white border) around the code when printed. A minimum of 4 modules of white space on all sides is recommended.
An “Access denied” result means the code is valid but access has been restricted. Check the following in QR Codes → select the code → Settings:
  • Disabled — the code has been manually turned off. Toggle it back to active.
  • Expiration date — the code’s validity period has ended. Update or remove the expiration date.
  • Scan limit reached — the maximum number of scans has been hit. Increase or remove the scan limit.
  • Password protection — the code requires a password. Confirm the intended audience has the correct password, or disable password protection if it was set unintentionally.
  1. Allow a few minutes — scan analytics are processed asynchronously and may take up to 5 minutes to appear in the dashboard after a scan.
  2. Check your plan — the Free plan includes basic scan count analytics only. Detailed analytics (location, device type, time-of-day breakdown) are available on Pro and above.
  3. If analytics are missing for scans you know occurred more than 30 minutes ago, contact support@aflux.io with the QR code name and approximate scan time.

​
Account & Billing

  1. Reset your password — on the login page, click Forgot password and follow the email instructions.
  2. Verify your email address — if you registered recently, check your inbox for a verification email. Your account will not be fully active until the address is confirmed.
  3. Clear browser cache and cookies — stale session data can block login. Try a hard refresh (Ctrl+Shift+R / Cmd+Shift+R) or an incognito window.
  4. Check for 2FA issues — if your account has 2FA enabled (Pro+) and you’ve lost access to your authenticator app, use the backup codes provided at setup, or contact support for account recovery.
After completing a plan upgrade, new limits and features usually activate within a few minutes.
  1. Wait 2–3 minutes, then do a hard refresh of the app (Ctrl+Shift+R / Cmd+Shift+R).
  2. Sign out and sign back in to force a fresh session with updated plan data.
  3. If the upgrade is still not reflected after 10 minutes, contact support@aflux.io with your account email and the date/time of the upgrade.
Per-module access control is a Pro and above feature. If a team member is unable to access a specific module:
  1. Go to Settings → Team → click the team member’s name → Permissions.
  2. Verify that access to the relevant module (E-Signature, Bulk Email, or QR Codes) is enabled for their role.
  3. Note that Guest role users have read-only access by default. Promote the user to Member or Admin if they need to take actions within a module.
If you are on the Free plan, per-member module permissions are not available. All users share the same access level. Upgrade to Pro to unlock granular team permissions.
Still stuck? Contact us at support@aflux.io — include your account email, a description of the issue, and any error messages you’ve seen so we can help you as quickly as possible.