Before you start
When a publication or restore shows a conflict warning.
- A teammate, another app or another operation may have changed the field.
- A conflict is a reason to inspect the newer value, not to force an overwrite.
- The draft and the current Shopify content can both contain useful changes.
Steps to follow
- Read the conflict message and refresh the current Shopify-backed value.
- Compare it with the draft or previous revision you wanted to use.
- Coordinate with anyone else editing that field.
- Keep or edit the intended wording using the available workflow, creating a fresh draft only when needed.
- Publish or restore only after the current target and desired value are clear.
For example
A colleague edits a product meta description after your draft was created. Publishing the older draft blindly would discard that newer work.
What happens next
The next successful write should reflect the reviewed current state. A conflict message alone does not publish the old draft.
A useful tip. Use History and Shopify together to understand what changed.
Take care. Do not repeatedly retry the same stale publication to bypass the warning.
Common questions
Does conflict mean the AI text is bad?
Not necessarily. It means the source or target value changed since the version you were using.
Should I generate again immediately?
First compare the current value and available draft. A new paid generation may not be necessary.
Can Restore also conflict?
Yes. Restoring a previous value can overwrite a newer edit, so it needs the same care.
If you are still stuck
- If you cannot identify the newer change or resolve the state, contact support with the resource and operation reference.