Before you start
Record the shop, time, affected action and visible error. Do not include credentials, full customer exports or unnecessary personal data.
A recognisable example
DYMR sees a publication timeout. The agency checks whether WooCommerce already accepted the change before attempting another publication.
Step by step
- Check whether normal visitors can still browse and purchase through the shop's own path. Then check source access and Daymerce access separately.
- Inspect the existing job, publication or handover result and compare with the source. An interrupted response does not establish whether the action was applied.
- Check recent changes, permission expiry, source credentials, capability support, scheduling and cache. Change one cause at a time and keep the original evidence.
- After recovery, refresh the relevant records and verify one complete affected task. Tell the owner what was confirmed and what remains unknown.
What you should see
You have a bounded diagnosis and a checked recovery. A temporary Daymerce outage is not the same as disconnecting the shop or removing Edge.
If it does not work
Still uncertain? Keep the job reference and sanitised steps for the responsible administrator. Pause repeated writes. Do not uninstall Edge as a first troubleshooting step, because local features may depend on it.
Menu names and available actions depend on your app language, permissions and connected shop. Screens show the real Daymerce interface with fictional DYMR data; original screen labels are preserved.