This article explains error messages you may see in the Ingrid Merchant Platform (IMP), what they mean, and what to do about them.
Error - changes not saved
What you see: you change a setting, and as soon as you click outside the field, IMP shows Error - changes not saved. It happens on every page you try to change, even after you refresh.
What it means: IMP saves every change in a draft first. This error usually means an earlier draft for your site got stuck in Ingrid's system, so IMP can't create a new one. The stuck draft is not visible in IMP, so you can't delete it yourself.
What to do:
Get the trace ID of the failed save: open your browser's developer tools, go to the Network tab, change the setting again, and click the request that failed (shown in red). Under Headers → Response Headers, copy the value of
x-trace-id. For more help, see How to get a trace or session ID?.Ask Iris, Ingrid's AI assistant, in the chat on the Ingrid Help Center. Include the error message, your site, the environment (stage or production), the page you tried to change and the trace ID. Iris hands your request over to the Ingrid team. If you can't reach Iris, email [email protected].
The Ingrid team removes the stuck draft. Then refresh IMP and make your change again.
Good to know: this is not caused by maintenance or by your permissions, so waiting or logging in again won't fix it.
Frequently asked questions
Will I lose my live settings?
No. Your published configuration stays live. Only the change you were trying to make is not saved.
Why can't I just delete the draft?
The stuck draft doesn't show in IMP, so there is nothing to delete from your side. The Ingrid team removes it for you.
Why do you need the trace ID?
It points the Ingrid team to the exact failed request, so they can find and fix the problem faster. Ingrid keeps stage logs for 7 days and production logs for 30 days, so send it soon.
