Error 401: Sorry you are not allowed to create resources

This error will appear when a Scheduled Order fails to process.

What this error means

This error means that the Wordpress Admin user who registered and connected the WooCommerce API to QPilot has been changed or deleted.

How to resolve this error

A Wordpress Administrator needs to reconnect your site's WooCommerce API to QPilot.

The Autoship Cloud plugin makes this easy to do with the following steps:

  1. Log in as an administrator, visit WP-Admin > Autoship Cloud > Settings
  2. Click "Disconnect"
  3. Follow the steps to Connect the WooCommerce API

After resolving this error

Any Scheduled Orders that failed for this issue should be retried as soon as possible to avoid disruption or confusion for your Autoship customers.

To retry a Scheduled Order, simply edit the Scheduled Order, set it's status back to Active and click "Update".

Any Scheduled Order that has a "next occurrence date" that is past and has a status of "Active" will be retried within 5-10 minutes.

Still Unresolved?  Update your API keys manually

If Disconnecting and Reconnecting is not successful in restoring your site's connection, you can also update your API keys manually.

  1. In WP-Admin go to WooCommmerce > Settings > Advanced > REST API
  2. Select Add Key
  3. Name your new API Key and ensure the key is:
    1. connected to a user with Administrator permissions
    2. enabled for Read/Write permissions
  4. Copy both the Consumer Key and Secret Keys (you may want to open another browser tab for this step)
    1. In your QPilot Merchant Account, edit the site you are connecting (see the Edit Site option by selecting the "three button icon" in the upper right of the site card)
    2. Paste the new Consumer Key and Secret Key into the General Settings tab
    3. Select "Update" to save your changes
  5. To confirm this was successful, you can visit WP-Admin > Autoship Cloud > Settings and select "Test Integration"
    1. If you receive a successful "200" response, the API key update worked.
    2. If not, please get in touch with support.

Here's a screen recording of what this looks like.

Still need help? Contact Us Contact Us