If you are seeing this message, your site is experiencing an error that is preventing the page for working correctly.
Page outdated [xxxxx]. Please refresh the page and retry.
This error needs to be identified and resolved. Below you’ll see what each error code means and the possible ways your site could be impacted.
ARTICLE CONTENT:
Why this error message appears
There are several reasons why an error message like this would be displayed on a page. The “fix” for each error message is different depending on what is causing the error.
Common causes for error messages:
- An outdated (or cached) page. For example, an order form is only valid for 24 hours, in case the backend pricing changed.
- Data corruption. If the database entries have been manually changed.
- AccessAlly bug. The error message contains a code that can be used for debugging.
The error codes can be found in the source code using the identifying string “/* — DEBUG ERROR CODE –*/”
Error categories
The guide below is designed to share more about what each code means. Noting the code you are seeing helps us help you when you reach out for support!
The first 2 digits of the error code identifies which area triggered the error.
| Code | Source |
|---|---|
| 01 | Credit card payment |
| 02 | Order processing |
| 03 | 1-click upsell |
| 04 | Paypal payment |
| 05 | Promo processing |
| 06 | Local order / subscription list |
| 07 | Ontraport order / subscription list |
| 08 | Infusionsoft order / subscription list |
| 09 | Password reset / snappy login |
| 10 | Local subscription operations |
| 11 | Team operations |
| 12 | User profile |
| 13 | User directory |
| 14 | Custom operations |
| 15 | Opt-in form |
| 16 | Affiliate info |
| 17 | User account (profile, address) update |
“01” Credit Card payments
| Code | Source |
|---|---|
| 01015 | Submit IP address doesn’t match starting order IP address. This is most likely caused by spam submission. |
| 01016 | Credit card request submitted out of order. This is most likely caused by spam submission. |
| 01017 | Missing recaptcha response. |
| 01018 | recaptcha code verification failed from Google API call. |
| 01019 | recaptcha code verification failed due to unknown reason. |
| 01020 | Intent ID was not provided to be inserted into the database. |
| 01021 | Required fields were not provided to update an intent. |
| 01022 | SCA redirect nonce check failed. |
| 01023 | SCA return nonce check failed. |
| 01024 | Missing SCA client secret. |
“02” Order Processing
| Code | Source |
|---|---|
| 02002 | Page Caching issue – we recommend turning off page caching on your order form pages. |
| 02008 | Open a support ticket for assistance |
| 02015 | Issue with Google reCAPTCHA keys |
If the error is 20011 or 02015 you can test by saving your existing reCAPTCHA keys in a safe place, then deleting them from your site. See where these are in your site at this article.
If order forms process after that with no hiccups you’re all set. If not, you may need to recreate new Google reCAPTCHA keys. (Article linked above.)
“09” Password Reset/Snappy Login
| Code | Source |
|---|---|
| 09001 | Missing mandatory data or nonce check fail when requesting a reset password link. Likely caused by outdated page. |
| 09005 | Missing mandatory data or nonce check fail when updating password. Likely caused by outdated page. |
| 09006 | Missing mandatory serialized data when updating password. Likely caused by outdated page. |
| 09007 | Current user does not exist. |
| 09008 | User not linked to a CRM contact. |
| 09009 | Current user cannot be validated when updating password. |
| 09010 | Order form does not exist. Likely caused by outdated page. |
| 09011 | Incorrect hash key during verification. |
| 09012 | Missing mandatory data or nonce check fail when signing in. Likely caused by outdated page. |
| 09013 | Missing mandatory serialized data when signing in. Likely caused by outdated page. |
| 09014 | Current user cannot be validated when signing in. |
“10” Credit Card Processing Errors
| Code | Source |
|---|---|
| 10013 | SCA (Strong Customer Authentication) Failed – ask client to update their credit card details. |
“14” Custom Operations
| Code | Source |
|---|---|
| 14019 | Add team member: generic frontend error. The backend error message is in the Team log. |
| 14027 | Team interaction: invalid team ID. |
| 14028 | Team interaction: invalid team interaction ID. |
| 14029 | Team interaction: the CRM contact ID is not a user in WordPress, thus no team interaction possible. |
| 14030 | Team interaction: the contact is not part of a team, ie. neither the team leader nor the team member. |
| 14031 | Custom operation with the specified ID does not exist. |
| 14032 | Custom operation with the specified ID is not a countdown timer. |
“17” CRM user account / address / credit card update
| Code | Source |
|---|---|
| 17001 | Profile update: missing mandatory data. Likely caused by outdated page. |
| 17002 | Profile update: nonce mismatch. Likely caused by outdated page. |
| 17003 | Profile update: user not linked to a CRM contact. |
| 17004 | Address update: missing mandatory data. Likely caused by outdated page. |
| 17005 | Address update: nonce mismatch. Likely caused by outdated page. |
| 17006 | Address update: user not linked to a CRM contact. |
| 17007 | Credit card update: missing mandatory data. Likely caused by outdated page. |
| 17008 | Credit card update: nonce mismatch. Likely caused by outdated page. |
| 17009 | Credit card update: user not linked to a CRM contact. |
| 17010 | Team update: team custom field does not exist in CRM. |
How to resolve this issue.
We recommend turning caching off on your order form pages. Your website hosting can assist you with this.
If you’re experiencing error messages unrelated to order forms contact us.
