Handle failed and pending items
POM Translate does not expose a generic Retry failed button. The correct next action depends on where the failure occurred and whether the string remains in the scheduled queue.
Read the failure first
The generation log can report:
- missing or empty provider output;
- changed protected formatting markers;
- source text changed while the request was running;
- a string over the machine-translation word limit;
- quota, licensing, service, or pause errors;
- a concurrent worker already processing the queue.
Unsafe, empty, or stale replies are not saved. Their strings remain pending.
Retry an immediate generation result
Correct the underlying cause, then select Translate pending only. Its database sweep finds missing rows, empty values, and entries with Pending status without repeating source discovery. If the failure occurred while parsing changed source content, use Process all instead. For a single string, use its row-level machine-translation control.
A source-change result should be retried only after the source edit is saved and stable. A protected-marker failure may require manual translation if the provider repeatedly changes required tokens.
Retry scheduled queue work
If the string remains under Strings already queued for machine translation, let WP-Cron continue or select Process now. Provider-quality failures are counted per string and locale. After repeated unusable replies reach the retry limit, the item is removed from the queue but remains pending for manual review.
If a string is no longer queued, edit it manually or run the pending generator after fixing the cause. Do not repeatedly resubmit quota, authorization, or structural errors without changing their underlying condition.