Tested on Google Chrome and Firefox, if an app has a link back to a draft order (eg: <a href=”https://admin.shopify.com/store-handle/draft_orders/123456” target=”_top”>Link to draft order, inside app</a>) , after merchant click the link in the app, and redirected to the draft order, and merchant make changes on the draft order and click “Save”, the “Save” button will be stuck there and keep appearing.
Demo video : CleanShot 2026-04-16 at 23.05.09
Merchants are blaming my app for this , but this seems like a Shopify platform issue, please look into this issue as soon as possible 
Update: not related to line item properties, it happens if my app redirects the merchant from my app page to the Shopify admin draft order details page, and then merchant make changes to the draft order, and click “Save”
Found a workaround, I need to use the app bridge navigation API :
shopify://admin/draft_orders/123456 , instead of https://admin.shopify.com/store/store_handle/draft_orders/123456
The workaround works as my app is embed app, for non-embed app, the issue still persist
Hi @soulchild,
Does the issue persist if you use the .myshopify.com URL for the redirect instead?
For example: https://<store_handle>.myshopify.com/admin/draft_orders/12345678910
Yes, the issue still persists if I use “.myshopify.com” URL for the link
Hi @soulchild,
Thanks for confirming it’s still persisting with the .myshopify.com URL.
I’ve tested this on my own store, with a freshly spun up test app, and I’m unable to replicate the behaviour in both an embedded and non-embedded app environment.
I’ve tested both embedded and non-embedded with .myshopify.com URLs and admin.shopify.com URLs, and with both target="_blank" and target="_top", and in all cases I was able to access the Draft Order in the admin from the link in the app UI, and successfully edit and save the Draft Order without any issues.
Since I’m not able to replicate this behaviour, and the fact that the error is occurring in the web admin directly, makes be think this is more of an Admin issue than an app issue.
In this case we’ll need you to reach out to our Shopify Support Team via the Shopify Help Center, so we can help you look into any admin issues that may be occurring in a more detailed, and fully authenticated support interaction.
If this is consistently replicable, please be sure to provide detailed replication steps for our support staff to help with efficient troubleshooting, and if it’s not consistently replicable, I’d recommend replicating it yourself before reaching out, and recording a HAR file showing any errors that may be returned in the browser developer tools console or network tab when the behaviour occurs.
Here’s some information on how to record a HAR file in the most popular browsers:
Note: HAR files can contain login information/credentials and session cookies. For data privacy purposes, please avoid entering/recording personal details such as passwords and credit card information. It would be best to record the HAR via an Incognito window.
Chrome
- Open the Developer Tools from the menu (Menu > More Tools > Developer tools), or by pressing Ctrl+Shift+C on your keyboard.
- Click on the Network tab.
- Look for a round button at the top-left of the Network tab. Make sure it is red. If it is grey, click it once to start recording.
- Check the box next to Preserve log.
- Use the clear button (a circle with a diagonal line through it) right before trying to reproduce the issue to remove any unnecessary information.
- Reproduce the issue (E.g. load/refresh the page that has errors, or perform the action that has errors).
- Save the capture by right-clicking on the grid and choosing Save as HAR with Content. Alternatively, you can click the export/save button (downward arrow with a line underneath).
Safari
- In Safari, go to the page where the HTTP(s) URL Sequence needs to be monitored.
- Enable Developers Tool by going to Safari > Preferences > Advance > Click Show Develop menu in menu bar
- In the menu bar at the top, click Develop and select Show Web Inspector.
- Click the Resources tab and enable Preserve Logs.
- Go to the Network tab.
- Reproduce the issue (E.g. load/refresh the page that has errors, or perform the action that has errors).
- After successfully performing the activity, lick the Export icon and save the HAR file.
Firefox
- In Firefox, go to the page where the issue is occurring.
- Click the Firefox menu available at the top-right of your browser window and select Web Developer → Network, or simply press the F12 button. The Developer Tools window opens as a docked panel at the side or bottom of Firefox.
- Click the Network tab.
- Click on Network Settings and enable Persist Logs.
- Now refresh the page and perform the activity that needs to be recorded i.e. the activity that produces the error.
- After successfully performing the activity, right-click on any row of the activity pane and select Save all as HAR or click the Export HAR icon and select Save all as HAR to download the HAR file.
Edge
- Open Microsoft Edge and navigate to the page where the issue is occurring. Note: This is tab and window dependent, so if the issue occurs in a new tab or window, the HAR recording needs to be done in that new tab or window.
- Click the horizontal ellipsis menu button and select More Tools, then click Developer Tools.
- Click the Network tab, and then click the Record button in the upper left corner of the tab and verify that it is red, if it is grey, click it to start recording.
- Check the box Preserve Log.
- Click the Clear button to clear out any existing logs from the Network tab. Note: Do not close the Developer Tools panel. This will end recording and the HAR file will be lost.
- Reproduce the issue while the network requests are being recorded.
- Once you have reproduced the issue fully, right-click anywhere on the grid of network requests and choose Save as HAR with Content, and save the file to the computer.