Split: Failed to parse because your job is above file limit of 1MB

This thread is resolved. Here is a description of the problem and solution.

Problem:
When attempting to update a translation by making slight changes to the original page and accessing the translation editor, an error occurs. This issue arises when the translation status is 'waiting for review,' preventing the translation job from updating.
Solution:
If you're experiencing this issue, we recommend you try the following steps:
1. Edit the page in the original language.
2. Make a small change and save it.
3. Go to WPML → Translation Management.
4. Find the page and send it for translation, choosing 'translate myself'.
5. Navigate to WPML → Translation and complete the translations from there.
This process should update the translation job for the page.

Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket at WPML support forum for further assistance.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

This topic is split from https://wpml.org/forums/topic/shortcode-translating-fluent-forms/

Tagged: ATE, Exception

This topic contains 20 replies, has 0 voices.

Last updated by Andrey 1 week, 1 day ago.

Assisted by: Andrey.

Author	Posts
March 31, 2025 at 11:53 am #16879106
Michael	Hey again Andrey, sorry to bother you again with that 1MB parse limit. But this error shows up again. See here: hidden link Love to have your help here. With kindness, Michael
March 31, 2025 at 1:05 pm #16879449
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Hello Michael, I'm sorry to hear that this issue has occurred again and that your client is unhappy. After watching your video, I noticed that your translation is currently in the status "waiting for review," which may be the reason the translation job hasn't been updated (including the custom field settings we configured). I believe that this should not happen with new pages or pages where we have already triggered translations. However, for this particular page, please try these steps: 1. Edit the page in the original language (German). 2. Make a small change and save it. 3. Go to WPML → Translation Management. 4. Find this page and send it for translation to French (select "translate myself"). 5. Navigate to WPML → Translation and translate from there to complete the translations. Following these steps should update the translation job for this page. I hope you also had a nice start to the week!
March 31, 2025 at 1:59 pm #16879777
Michael	Hey again Andrey, nope. I did it exactly as you said. And even when going into the orig. language page with "Edit page" and then go to Wpml ---> translation and clicking on the "eye" (for translating) there is an error showing up. Also when manually checking the french version with "modify the translation" I get the parse 1MB limit error - see 2nd screenshot. Feel free Andrey to check yourself as you have the credentials to login to the site. Cheers, Michael
March 31, 2025 at 3:19 pm #16880078
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Could you please check now? I have followed the steps in my previous message, but I have also set the custom field _uabb_batch_backup_fl_builder_data to Don't translate. I do not think there's anything to translate.
April 1, 2025 at 12:43 pm #16882884
Michael	Yes - it seems to work again. Lets hope it stays that way. 👌Thanks for your input Andrey! I see there are a few fields also translated that would not be necessary - see screenshot. These seem to come from the Astra theme (or Astra Pro)... looks like mainly color informations and some background image or background color settings. Should we see to these as well? Cheers, Michael
April 1, 2025 at 1:02 pm #16883007
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Lets hope it stays that way. 👌Thanks for your input Andrey! I hope too 🙂 I see there are a few fields also translated that would not be necessary - see screenshot. These seem to come from the Astra theme (or Astra Pro)... looks like mainly color informations and some background image or background color settings. Should we see to these as well? The approach depends on the content's origin. If the content consists of custom fields, you can set them to "Copy" (as we did before). However, if it is part of a different element, such as text with specific settings, it may be challenging to distinguish what should be included in the translation.