Finalsite CMS Error Codes Guide

Usually self-resolves within minutes. While waiting:

• Wait 1-2 minutes and refresh
• Check status.finalsite.com
• If it persists more than 15 minutes, contact Support with the Cloudflare Ray ID from the error page

Triggered by an unusual request pattern or rate limit.

• Note the Cloudflare Ray ID on the error page
• Clear browser cache and cookies, then retry
• Contact Support with the Ray ID to review the block

Submitted content triggered a WAF security rule.

• Copy the Error ID shown on the page
• Contact Support with the Error ID and what was being done when it appeared

May be a server issue, maintenance, or DNS misconfiguration.

• Check status.finalsite.com for an active incident
• If no incident is posted, contact Support with the site URL and time it started

Social platform crawler (Facebook, LinkedIn) blocked by the WAF when fetching link preview metadata.

• Verify the page URL is publicly accessible
• Test with the Facebook Sharing Debugger
• If the debugger also returns 403, contact Support: a WAF rule exception may be needed

A single Content element exceeded 75,000 characters, often from pasting external content.

• Paste the element's content into a text editor to check length
• Split it across multiple Content elements
• Remove hidden HTML or formatting that adds extra characters

Wrong org type, incomplete info, or payment issue at the $99 enrollment step.

• Confirm "Educational Institution" as the organization type
• Verify the Apple ID has a valid payment method
• Contact Support with a screenshot if it persists

May be a timezone mismatch, misconfigured filters, or large event set.

• Check that the element's timezone matches the school's timezone
• Tighten date filters to reduce events loaded
• Remove and re-add the element to reset its configuration
• Contact Support if the issue persists

May be a temporary upstream AI service issue.

• Refresh the page and try again
• Check status.finalsite.com for active incidents
• Contact Support with the page URL and expected vs. actual behavior

Upload speed is too slow to complete within the session timeout window.

• Compress or resize the file (images under 2 MB)
• For video, use a YouTube or Vimeo embed instead
• Upload from a wired connection and during off-peak hours

Payment was flagged at the processor level: it is unclear whether it processed.

• Do not re-run the payment
• Check with the cardholder whether funds were debited
• Contact Support with the form submission ID to check processor logs

Multiple causes depending on the symptom.

• Not saving: confirm all required fields are filled and the form is set to Active
• Not exporting: check date range filters on the Submissions tab
• Deleted form: contact Support immediately: deleted forms may be recoverable within a limited window

Address was added to a suppression list after a prior bounce, complaint, or unsubscribe.

• Do not re-send without resolution
• Contact Support with the affected email address to request a suppression review

US carriers require SMS traffic to be registered under 10DLC. Messages are blocked if the account is unregistered or the campaign was rejected.

• Contact Support to check 10DLC registration status
• Do not retry screened messages: repeated sends may worsen filtering
• If recently registered, allow 24-72 hours for carrier propagation

Usually a missing required field, permission issue, or timezone mismatch.

• Confirm subject line, recipient group, and scheduled time are all set
• Verify the account has Send permission for this message type
• Ensure the scheduled time is in the future for the account timezone
• Try saving as draft, refreshing, then reopening

Counts sync on a delay after imports, manual adds, or role changes. Totals may also differ from send-eligible counts (inactive or unverified accounts are excluded).

• Wait a few minutes and refresh
• Check whether the discrepancy is total members vs. send-eligible members
• If still wrong after 30 minutes, contact Support with the group name and both numbers