Understanding your integration Activity Log (errors explained)

Sign Customiser keeps an Activity Log for the integrations in the list below. The log lists the requests between Sign Customiser and your store or website. Sign Customiser makes these requests when it checks a WooCommerce connection, registers WooCommerce webhooks, creates a custom sign product, tags a Shopify order, or repairs or renames Shopify collections for a customiser. Your store or site also sends requests to Sign Customiser, such as a customised order. These show an Incoming Request badge. The entry heading is “Incoming request” for a customised order, or “WooCommerce webhook received”, “Wix webhook received” or “Shopify webhook received” for a store webhook.

The Activity Log applies to these integrations:

• Shopify

• WooCommerce

• Wix

• Custom API

Webhooks, including Zapier, keep their own log. Squarespace and Webflow are not integration types in Sign Customiser, so they have no integration page. The page of an Etsy integration has no Activity Logs section.

Not every entry means that something is broken. Some entries are informational. We record them for transparency. For the entries in the first group below, Sign Customiser still creates your product and publishes it to your Online Store. A skipped market publication can mean that the product is not published to that market. Use this page to find what each entry means.

Entries stay in the log for about seven days. Sign Customiser removes older requests automatically.

Where to find the Activity Log

• Shopify: open the app that you installed for Sign Customiser in your Shopify admin. On the Home page, in the Menu card, click Tools & Settings. Then click Integrations and Webhooks. Click View Details on your enabled Shopify integration. The Activity Logs section is on that page.

• WooCommerce, Wix and Custom API (Universal): log in to Sign Customiser. In the left sidebar, under Integrate, click Integrations. Click View Details on your enabled integration.

• Zapier and other webhooks: go to Integrate, then Integrations. In the Configured webhooks table, click the topic. The Webhook Details page has an Activity Logs section.

Each log entry shows a description, the request method, the time and, when there is one, the status code. A “Shopify collection membership recovery” entry shows its recovery badge instead, and its 409 status is under Response Details. To show the entries for one customiser, use the customiser list. The default value is All Customisers. On an integration, use the filter that shows All Logs by default to select All Logs or Errors Only.

Click View Details on an entry to open Request/Response Details. For a “Shopify collection membership recovery” entry, the window is titled Recovery details. This window shows the method and destination URL of the request. For an outgoing webhook, the URL shows only the scheme, host and port. For an incoming request or a store webhook, the URL is the address that Sign Customiser received. The window also shows the headers and, when there is one, the status of the response. For an outgoing request or webhook, Sign Customiser does not keep the response body from your store, site or endpoint. The response Body shows “redacted”, or “N/A” when the entry has no response body. For an incoming request or a store webhook, the Body shows the response that Sign Customiser sent back. The exception for outgoing entries is an entry that Sign Customiser writes itself, such as a “Shopify managed collection status” or “Shopify collection membership recovery” entry. Its Body shows a short message from Sign Customiser. The Body shows “N/A” for a connection failure on a Shopify, WooCommerce, Wix or Custom API request. It also shows “N/A” for a “Shopify media readiness poll” entry and a “Shopify market publication lookup skipped” entry. To read the exact message from your site, look in your own server logs.

Errors Only and the home-page banner

On an integration page, Errors Only lists every entry that has a 4xx or 5xx status code. It shows “Showing x to y of z logs” at the bottom. It includes the informational entries that this article describes with status 408, 409 and 424.

The Recent Integration Errors banner on your Home page works differently. It counts the errors that need action and are still in the log, for example “3 errors in the last 7 days”. It does not count the informational entries below. To open the log with Errors Only selected, click View Details on the banner.

Connection failures and timeouts have no status code. They show under All Logs only. They do not show under Errors Only.

Informational: usually no action needed

“Shopify market publication lookup skipped” (status 424, recorded by Sign Customiser) — Shopify. Your product was created and published to your Online Store normally. We also try to publish it to a Shopify Market. We skip this optional step in these cases:

• No market information was supplied.

• The optional Markets permission is not approved.

• Shopify did not return the market catalogue.

• The market catalogue lookup failed with an error.

• Publishing to the market failed.

We also skip the step when the market has no active catalogue publication. That case writes no entry.

Take action only if you sell through Shopify Markets and a product is not published to a market that you sell in. If the Home page of your Sign Customiser app shows the Approve Shopify Markets access banner, select Approve Shopify Markets access. If add to cart fails only for shoppers in some countries, see Why is add to cart not working?.

“Shopify media readiness poll” (status 408, recorded by Sign Customiser) — Shopify. We waited for Shopify to finish processing a product image. We checked up to five times, 200 milliseconds apart, while we created your product. The image was not ready in that time, or Sign Customiser could not reach Shopify to check it, so we stopped checking. Your product is still created.

“Shopify collection membership recovery” (status 409, recorded by Sign Customiser) — Shopify. Shopify did not attach the managed collection membership to your product. The badge shows Recovery in progress or Recovery completed. Sign Customiser restores the collection membership automatically.

These entries can show under Errors Only.

A 408 or 424 on any other entry is not informational. Check that entry.

Needs action: permissions and authentication

Missing permission — Shopify. A required permission is not accepted, so publishing the product to your Online Store can fail. The entry description is Outgoing request. Shopify can report a failed publish inside a status 200 response. In that case the entry shows a 200 badge. Check All Logs. Errors Only does not list an entry with a 200 badge. For the steps to fix this, see Missing Permissions.

Status 401 or 403 — custom / Universal. Your endpoint refused the request. Sign Customiser signs each Custom API request with the Integration Secret of your integration, and each webhook delivery with the secret of that webhook. Both signatures are sent in the X-Webhook-Signature header. Check how your endpoint verifies the signature. You can see the Integration Secret on your integration page. See Custom API Integration.

Needs action: limits and validation

Daily variant limit — Shopify. Shopify limits how many new product variants a store can create each day. After a store reaches 500,000 product variants, it can create no more than 10,000 new variants each day. This limit does not apply to stores on the Shopify Plus plan. When Shopify reports this limit, the product creation fails. Sign Customiser cannot create new custom products while the limit applies. The entry in the log is an Outgoing request. Its badge is the HTTP status that Shopify returned. Check All Logs. Errors Only lists this entry only when its badge is a 4xx or 5xx status. The log entry does not show the message from Shopify, because Sign Customiser does not keep the response body. Look for the email instead. Sign Customiser sends an email to the contact address of your customiser with the subject “Shopify daily variant limit reached - Sign Customiser”. It sends this email at most once in 24 hours.

Add to cart fails for shoppers — Shopify. This log does not record failed add-to-cart attempts from the browser of the shopper. If add to cart fails for shoppers, check the causes in Why is add to cart not working?, such as Incomplete Location Fulfilment.

Status 422 — custom / Universal. Your endpoint rejected the product payload. The log does not keep the response body. Look in your own server logs for the validation message.

Status 429. The destination asked us to slow down because too many requests were made in a short time. A short wait does not clear the daily variant limit. See Daily variant limit above.

Needs action: server and connection errors

Status 500 to 599. Shopify or your own server returned an error while we created the product. For custom integrations, look in your server logs for the exact message. Some 503 entries are written by Sign Customiser itself, not by Shopify. Examples are “Shopify managed collection ensure failed” and “Shopify managed collection rename failed”. They mean that Sign Customiser could not prepare or rename a Shopify collection. Sign Customiser tries again later.

Connection failed or timeout (“Outgoing request failed” or “Webhook request failed”). We could not reach your endpoint. This entry has no status code, so it shows under All Logs only. Check that the URL is correct and that people can reach it. For a custom integration or a webhook, Sign Customiser waits up to 15 seconds for a response. Check that your server responds in that time. For webhooks, see Subscribe to Webhooks.

How to read the status code

• 2xx: the server answered, unless Sign Customiser wrote the entry itself. A 200 on a “Shopify managed collection status” entry is a notice from Sign Customiser (for example, a Shopify plan without collection support). A 200 on a “Shopify propagation wait” entry is a timing record from Sign Customiser. Neither is a reply from Shopify. Shopify can also report an error inside a status 200 response.

• 408 or 424 on a “Shopify media readiness poll” or “Shopify market publication lookup skipped” entry: informational. Act on a 424 only when a product is not published to a market that you sell in. A 408 or 424 on any other entry needs checking.

• 409 on a “Shopify collection membership recovery” entry: informational.

• Other 4xx (for example 400, 401, 403, 404, 422, 429): the destination refused the request.

• 5xx: a server error, on the Shopify side or on your own server. A 503 on a Shopify managed collection entry is set by Sign Customiser itself when it cannot prepare or rename a collection.

• No status code: we could not reach your endpoint.

Still not sure?

Open View Details on the entry. Copy the description and the status code. Send them to us in the chat. Our support chat can look up the activity log of your customisers, and the description and status code help us find the entry. Do not use the error count alone.