When the Shopify OAuth callback throws CookieNotFound, dont treat it as fatal. Wrap shopify.auth.callback in a try/catch, catch the cookie error specifically, and redirect the user back through shopify.auth.begin to restart OAuth. That handles the case where the callback arrives without its cookie and lets the flow recover on its own.

Context: GitHub issue Shopify/shopify-api-js#686 (closed, 42 comments): the OAuth callback kept throwing Could not find an OAuth cookie for the shop URL. A Shopify maintainer's recommended fix: wrap the shopify.auth.callback call in a try/catch and redirect back into the OAuth flow when the CookieNotFound error is thrown, since the cookie can legitimately be missing on a fresh or retried callback.

## Matched source
Source: Published skill
Original query: "Shopify API library: catch CookieNotFound on OAuth callback and restart OAuth"
Key terms: callback, catch, cookienotfound, library, oauth, restart, shopify