Error Codes
v2.10 Your WordPress dashboard
The Task History screen on your WooCommerce store shows all Trigger and Action tasks, as well as any errors that may have occurred.
The Task History screen is located at WordPress Dashboard → WooCommerce → Zapier → Task History.
Errored tasks are shown with a red Error status:
Hovering over the Error Task will show the error code, and clicking on the Get Help link will take you to the relevant error documentation.
Each error has a unique error code, which can be used to identify the cause of the error.
Common Error Codes¶
The most commonly occurring error codes are listed below, along with solutions to resolve them.
- Common Error Codes
- action_scheduler_failure
- http_request_failed
- order_invalid_parent_id
- rest_invalid_param
- rest_missing_callback_param
- trigger_error_response
- woocommerce_rest_cannot_view
- woocommerce_rest_invalid_id
- woocommerce_rest_invalid_customer_id
- woocommerce_rest_invalid_wc_user_membership_id
- woocommerce_rest_order_invalid_id
- woocommerce_rest_product_invalid_id
- woocommerce_rest_shop_coupon_invalid_id
- woocommerce_rest_shop_order_invalid_id
- woocommerce_rest_invalid_shipping_item
- woocommerce_rest_product_stock_management_disabled
action_scheduler_failure
¶
The action_scheduler_failure
error occurs when a Zapier Integration for WooCommerce encounters an issue while attempting to send data to Zapier.com. This error is related to the Action Scheduler, a library WooCommerce uses to manage and schedule tasks.
View the Task History record that has the Error status, and more details about the error will be available in the Message column.
Click on the relevant error message below for the next steps.
Action Scheduler Failure: action marked as failed after 300 seconds. Unknown error occurred. Check server, PHP and database error logs to diagnose cause.
This error message indicates that the Action Scheduler could not complete the task within the default timeout period of 300 seconds (5 minutes). There are several potential causes for this error:
- Server resources: The server may need more resources (e.g., CPU, memory) to process the task within the allotted time. This can happen if the server is under heavy load or if the task is particularly resource-intensive.
- Network issues: If there are network connectivity problems between your server and Zapier.com, the task may fail to complete within the timeout period. This can be due to slow network speeds, high latency, or intermittent connectivity issues.
- Plugin conflicts: Conflicts with other WordPress plugins or themes can sometimes interfere with the Action Scheduler’s ability to complete tasks on time. Deactivating other plugins and switching to a default theme can help identify if this is the cause.
Troubleshooting¶
To diagnose the specific cause of the action_scheduler_failure
error, follow these steps:
- Examine your WooCommerce logs.
- Check your server’s error logs (e.g., Apache, Nginx) for relevant error messages or warnings.
- Review your PHP error logs for any PHP-related issues, such as fatal errors, warnings, or notices.
- Consult the Failed Tasks documentation for additional troubleshooting steps and guidance on resolving Action Scheduler failures.
http_request_failed
¶
The http_request_failed
error occurs when Zapier Integration for WooCommerce encounters a problem while attempting to send data to Zapier.com. This error indicates that the HTTP request from your WooCommerce store to Zapier.com has failed.
View the Task History record that has the Error status, and more details about the error will be available in the Message column.
Click on the relevant error message below for the next steps.
Communication error with zapier.com: cURL error 28: Operation timed out after x milliseconds with 0 bytes received
This specific error message suggests that the network connection between your website and Zapier.com timed out. The request was unable to complete within the specified timeout period, resulting in the http_request_failed
error.
There are several potential causes for this error:
- Heavy website load: If your website is experiencing a high volume of traffic or resource-intensive tasks, it may be unable to process the request to Zapier.com on time, leading to a timeout.
- Slow server performance: If your website is hosted on a slow or underperforming server, it may struggle to send the request to Zapier.com within the timeout period.
- Zapier.com availability issues: If Zapier.com is experiencing outages, downtime, or performance problems, it may be unable to respond to the request from your WooCommerce store on time, resulting in a timeout.
- Network connectivity issues: Intermittent network problems, such as high latency or packet loss, between your website and Zapier.com can cause requests to time out.
Troubleshooting¶
To diagnose and resolve the http_request_failed
error, follow these steps:
- Check your website’s server load and performance metrics.
- Verify that your website is hosted on a reliable and well-optimized server.
- Monitor the Zapier.com status page to see any reported outages or performance issues that could be causing the timeouts. If there is an ongoing issue, wait until Zapier.com resolves it before proceeding.
- Examine your WooCommerce logs for any additional information or context related to the error, which may help identify the cause of the issue.
- If the issue persists, consult the Zapier Service Outages documentation for additional troubleshooting steps and guidance on resolving Zapier.com-related issues.
order_invalid_parent_id
¶
The order_invalid_parent_id
error occurs when attempting to create or update an order in WooCommerce, and the specified parent order ID is either invalid or does not exist. This error indicates that the provided parent order ID does not correspond to a valid order in your WooCommerce store. There are a few potential causes for this error:
- Incorrect parent order Id: The most common cause is providing an incorrect parent order ID. Double-check that the ID you are using matches an existing WooCommerce order.
- Deleted parent order: If the parent order was previously deleted from your WooCommerce store, attempting to reference it will result in this error. Ensure that the parent order you are trying to use has not been removed.
- Incorrect store or environment: If you are using multiple WooCommerce stores or environments (e.g., staging, production), make sure you are using the correct parent order ID for the corresponding store or environment.
Troubleshooting¶
To resolve the order_invalid_parent_id
error, follow these steps:
- Verify that the Parent ID field is set to the correct ID of an existing WooCommerce order.
- Check your WooCommerce store’s orders to confirm that the parent order you are trying to use exists and has not been deleted.
- If you are using multiple stores or environments, ensure that you are using the correct parent order ID for the intended store or environment.
rest_invalid_param
¶
The rest_invalid_param
error occurs when a request to the API contains an invalid parameter. This error indicates that one or more parameters provided in the request are either missing, have an incorrect format, or contain invalid values.
View the Task History record that has the Error status, and more details about the error will be available in the Message column.
Troubleshooting¶
To resolve the rest_invalid_param
error, follow these steps:
- Check the error message to identify which fields are causing the issue.
- Examine your Zapier Integration for WooCommerce logs and your WordPress and server error logs for any additional information or context related to the error. Look for specific details about the invalid parameter and the surrounding circumstances.
- If you use custom code or plugins that interact with the WordPress REST API, review the code to ensure that it is correctly constructing the requests and handling any error responses appropriately.
rest_missing_callback_param
¶
The rest_missing_callback_param
error occurs when a required field is missing from the data sent to WooCommerce. This error indicates that the request is incomplete and cannot be processed due to the absence of one or more mandatory parameters.
Common error messages associated with this error code include:
- “Error creating Customer via Create Customer action. Missing parameter(s): email”
- “Error creating Order Note via Create Order Note action. Missing parameter(s): order_id, note”
- “Error updating Product via Update Product Price action. Missing parameter(s): price_value”
- “Error creating User Membership via Create User Membership action. Missing parameter(s): customer_id, plan_id”
The error typically occurs when all the required fields in the Create action step are not populated. Required fields are usually marked with an asterisk (*) or described as mandatory in the action’s documentation. Required fields are sometimes dynamically determined based on the provided data.
Troubleshooting¶
To resolve the rest_missing_callback_param
error, follow these steps:
- View the Task History record that has the Error status, and more details about the error will be available in the Message column. Look for specific details about the missing parameter(s) or field(s), such as “email” for the Create Customer action, “order_id” and “note” for the Create Order Note action, “price_value” for the Update Product Price action, or “customer_id” and “plan_id” for the Create User Membership action.
- Edit your Zap’s Create action step and review all the required fields. Ensure that each required field is populated with a valid value.
trigger_error_response
¶
The trigger_error_response
error occurs when Zapier Integration for WooCommerce encounters an unexpected error while attempting to send data to Zapier.com. This error indicates that Zapier.com has responded with an unexpected error message.
Click on the relevant error message below for the next steps.
There are several potential causes for this error:
- Zapier.com availability issues: If Zapier.com is experiencing outages, maintenance, or other availability problems, it may respond with unexpected error messages. This can happen if Zapier.com’s servers are down, overloaded, or undergoing updates.
- Network issues: Intermittent network connectivity problems between your server and Zapier.com can sometimes result in unexpected error responses from Zapier.com.
Troubleshooting¶
To diagnose and resolve the trigger_error_response
error, follow these steps:
- Check the Zapier.com status page to see if any reported outages or issues could be causing the error. If there is an ongoing issue, wait until Zapier.com resolves it before proceeding.
- Examine your WooCommerce logs for more details about the specific error response received from Zapier.com. This information can help you identify the cause of the error and determine the appropriate course of action.
- View the Task History record that has the Error status, and more details about the error will be available in the Message column.
- If the issue persists, consult the Zapier Service Outages documentation for additional troubleshooting steps and guidance on resolving Zapier.com-related issues.
woocommerce_rest_cannot_view
¶
This occurs when a WooCommerce webhook (Trigger) was created by a WordPress user that no longer exists.
woocommerce_rest_invalid_id
¶
This error is a WooCommerce error that occurs when an ID field is null, empty, or points to a non-existent resource.
The error typically occurs when the Create Subscription Note action is triggered with an ID that does not correspond to an existing subscription in your WooCommerce store.
There are a few potential causes for this error:
- Incorrect ID: The most common cause is providing an incorrect ID. Double-check that the ID you are using matches an existing resource.
- Deleted resource: If the resource was previously deleted from your WooCommerce store, attempting to update it will result in this error. Ensure the resource you are trying to update has not been removed.
- Incorrect store or environment: If you are using multiple WooCommerce stores or environments (e.g., staging, production), make sure you are using the correct resource ID for the corresponding store or environment.
Troubleshooting¶
To resolve the woocommerce_rest_invalid_id
error when updating resource, follow these steps:
- Verify that the ID provided in the action is correct and matches an existing resource.
- Check your WooCommerce store’s resources to confirm that the resource exists and has not been deleted.
- If you are using multiple stores or environments, ensure that you are using the correct resource ID for the intended store or environment.
woocommerce_rest_invalid_customer_id
¶
This error is a WooCommerce error that occurs when an ID field is null, empty, or points to a non-existent Customer.
This error occurs when attempting to use the Update Customer action with an invalid or non-existent customer ID. This error indicates that the provided customer ID does not correspond to any existing customer in your WooCommerce store.
There are a few potential causes for this error:
- Incorrect ID: The most common cause is providing an incorrect ID. Double-check that the ID you are using matches an existing Customer.
- Deleted resource: If the Customer was previously deleted from your WooCommerce store, attempting to update it will result in this error. Ensure the Customer you are trying to update has not been removed.
- Incorrect store or environment: If you are using multiple WooCommerce stores or environments (e.g., staging, production), make sure you are using the correct Customer ID for the corresponding store or environment.
Troubleshooting¶
To resolve the woocommerce_rest_invalid_customer_id
error when updating Customer, follow these steps:
- Verify that the ID provided in the action is correct and matches an existing Customer.
- Check your WooCommerce store’s resources to confirm that the Customer exists and has not been deleted.
- If you are using multiple stores or environments, ensure that you are using the correct Customer ID for the intended store or environment.
woocommerce_rest_invalid_wc_user_membership_id
¶
This error is a WooCommerce error that occurs when an ID field is null, empty, or points to a non-existent User Membership.
This error occurs when attempting to update a user membership using the Update User Membership action, and the specified user membership ID is either invalid or does not exist. This error indicates that the provided user membership ID does not correspond to a valid user membership in your WooCommerce store.
There are a few potential causes for this error:
- Incorrect ID: The most common cause is providing an incorrect ID. Double-check that the ID you are using matches an existing User Membership.
- Deleted resource: If the User Membership was previously deleted from your WooCommerce store, attempting to update it will result in this error. Ensure the User Membership you are trying to update has not been removed.
- Incorrect store or environment: If you are using multiple WooCommerce stores or environments (e.g., staging, production), make sure you are using the correct User Membership ID for the corresponding store or environment.
Troubleshooting¶
To resolve the woocommerce_rest_invalid_wc_user_membership_id
error when updating User Membership, follow these steps:
- Verify that the ID provided in the action is correct and matches an existing User Membership.
- Check your WooCommerce store’s resources to confirm that the User Membership exists and has not been deleted.
- If you are using multiple stores or environments, ensure that you are using the correct User Membership ID for the intended store or environment.
woocommerce_rest_order_invalid_id
¶
This error is a WooCommerce error that occurs when an ID field is null, empty, or points to a non-existent Order Note.
The error typically occurs when the Create Order Note action is triggered with an ID that does not correspond to an existing order in your WooCommerce store.
There are a few potential causes for this error:
- Incorrect ID: The most common cause is providing an incorrect ID. Double-check that the ID you are using matches an existing Order Note.
- Deleted resource: If the Order Note was previously deleted from your WooCommerce store, attempting to update it will result in this error. Ensure the Order Note you are trying to update has not been removed.
- Incorrect store or environment: If you are using multiple WooCommerce stores or environments (e.g., staging, production), make sure you are using the correct Order Note ID for the corresponding store or environment.
Troubleshooting¶
To resolve the woocommerce_rest_order_invalid_id
error when updating Order Note, follow these steps:
- Verify that the ID provided in the action is correct and matches an existing Order Note.
- Check your WooCommerce store’s resources to confirm that the Order Note exists and has not been deleted.
- If you are using multiple stores or environments, ensure that you are using the correct Order Note ID for the intended store or environment.
woocommerce_rest_product_invalid_id
¶
This error is a WooCommerce error that occurs when an ID field is null, empty, or points to a non-existent Product.
This error occurs when attempting to use the Update Product Price action or Update Product Stock Quantity action with an invalid or non-existent product ID. This error indicates that the provided product ID does not correspond to any existing product in your WooCommerce store.
There are a few potential causes for this error:
- Incorrect ID: The most common cause is providing an incorrect ID. Double-check that the ID you are using matches an existing Product.
- Deleted resource: If the Product was previously deleted from your WooCommerce store, attempting to update it will result in this error. Ensure the Product you are trying to update has not been removed.
- Incorrect store or environment: If you are using multiple WooCommerce stores or environments (e.g., staging, production), make sure you are using the correct Product ID for the corresponding store or environment.
Troubleshooting¶
To resolve the woocommerce_rest_product_invalid_id
error when updating Product, follow these steps:
- Verify that the ID provided in the action is correct and matches an existing Product.
- Check your WooCommerce store’s resources to confirm that the Product exists and has not been deleted.
- If you are using multiple stores or environments, ensure that you are using the correct Product ID for the intended store or environment.
woocommerce_rest_shop_coupon_invalid_id
¶
This error is a WooCommerce error that occurs when an ID field is null, empty, or points to a non-existent Coupon.
This error occurs when attempting to use the Update Coupon action with an invalid or non-existent coupon ID. This error indicates that the provided coupon ID does not correspond to any existing coupon in your WooCommerce store.
There are a few potential causes for this error:
- Incorrect ID: The most common cause is providing an incorrect ID. Double-check that the ID you are using matches an existing Coupon.
- Deleted resource: If the Coupon was previously deleted from your WooCommerce store, attempting to update it will result in this error. Ensure the Coupon you are trying to update has not been removed.
- Incorrect store or environment: If you are using multiple WooCommerce stores or environments (e.g., staging, production), make sure you are using the correct Coupon ID for the corresponding store or environment.
Troubleshooting¶
To resolve the woocommerce_rest_shop_coupon_invalid_id
error when updating Coupon, follow these steps:
- Verify that the ID provided in the action is correct and matches an existing Coupon.
- Check your WooCommerce store’s resources to confirm that the Coupon exists and has not been deleted.
- If you are using multiple stores or environments, ensure that you are using the correct Coupon ID for the intended store or environment.
woocommerce_rest_shop_order_invalid_id
¶
This error is a WooCommerce error that occurs when an ID field is null, empty, or points to a non-existent Order.
This error occurs when using the Update Order action with an invalid or non-existent order ID. This error indicates that the provided order ID does not correspond to any existing WooCommerce order in your store.
There are a few potential causes for this error:
- Incorrect ID: The most common cause is providing an incorrect ID. Double-check that the ID you are using matches an existing Order.
- Deleted resource: If the Order was previously deleted from your WooCommerce store, attempting to update it will result in this error. Ensure the Order you are trying to update has not been removed.
- Incorrect store or environment: If you are using multiple WooCommerce stores or environments (e.g., staging, production), make sure you are using the correct Order ID for the corresponding store or environment.
Troubleshooting¶
To resolve the woocommerce_rest_shop_order_invalid_id
error when updating Order, follow these steps:
- Verify that the ID provided in the action is correct and matches an existing Order.
- Check your WooCommerce store’s resources to confirm that the Order exists and has not been deleted.
- If you are using multiple stores or environments, ensure that you are using the correct Order ID for the intended store or environment.
woocommerce_rest_invalid_shipping_item
¶
The woocommerce_rest_invalid_shipping_item
error occurs when attempting to create an order shipping method, but the required Shipping Lines → Method Id field is missing or invalid. This error indicates that the shipping method cannot be created or updated due to insufficient or incorrect data.
Troubleshooting¶
To resolve the woocommerce_rest_invalid_shipping_item
error, follow these steps:
- Verify that the Shipping Lines → Method Id field is included in the request payload when creating a new shipping method.
- Ensure the Method ID field contains a valid and existing shipping method ID from your WooCommerce store.
woocommerce_rest_product_stock_management_disabled
¶
The woocommerce_rest_product_stock_management_disabled
error occurs when attempting to use the Update Product Stock Quantity action on a product that does not have stock management enabled in WooCommerce. This error indicates that the product’s inventory settings are not configured to manage stock levels.
The error typically occurs when the Update Product Stock Quantity action is triggered for a product with the “Manage stock” option turned off in its WooCommerce inventory settings.
There are a few potential causes for this error:
- Stock management not enabled: The most common cause is that the product’s inventory settings do not enable the “Manage stock” option. By default, WooCommerce products do not enable stock management unless explicitly turned on.
- Incorrect product ID: This error will occur if the product ID provided in the Update Product Stock Quantity action does not match a product with stock management enabled. Ensure that the correct product ID is being used.
- Product type incompatibility: Certain product types in WooCommerce, such as virtual or downloadable products, may not have stock management options. Attempting to update the stock quantity for these product types can result in the
woocommerce_rest_product_stock_management_disabled
error.
Troubleshooting¶
To resolve the woocommerce_rest_product_stock_management_disabled
error, follow these steps:
- Edit the affected product in your WooCommerce store’s admin area.
- Navigate to the product’s “Inventory” tab in the “Product Data” section.
- Ensure that the “Manage stock?” option is checked. This enables stock management for the product.
- Save the product changes.
- Retry the Update Product Stock Quantity action to ensure it can successfully update the product’s stock quantity.
If you have verified that stock management is enabled for the product, but the error persists, consider the following additional steps:
- Double-check that the correct product ID is used in the Update Product Stock Quantity action.
- Verify that the product type supports stock management. Stock management may not be applicable if the product is virtual or downloadable.