HTTP NODE with predefined woocommerce credentials not working

Describe the problem/error/question

Im creating an AI support agent , it has a tool which is a subworkflow that is pasted below.
this subworkflow is wthe problem. when i run it it stops at the http node get_product and the output is empty . when i hover over the node in execution preview it shows the creds problem like in the screenshot , however the credsare setup correctly
when i manually execute the node it works fine, when it is executed in production it does not work
what should i do ??

What is the error message?

Please share your workflow

Share the output returned by the last node

It shows nothing

Information on your n8n setup

Self hosted with docker
n8n Version
2.16.0

welcome to the n8n community @Ilyes_Haddad
I’d first make sure both the main workflow and the subworkflow/tool are saved and published, and that the same credential is selected in the HTTP node, because production always uses the currently published version. Then I’d inspect one failed production execution, or re-run it with past execution data, to verify that the HTTP node is actually receiving the same input in production as it does in manual testing. If you’re running queue mode, I’d also check whether the worker has the same network access and environment setup as the main instance, since production executions run on workers.

Hello @Ilyes_Haddad welcome to the community,

The issue is that your WooCommerce credentials are configured but not actually linked to the node inside the subworkflow. You can see this in the screenshot where it says “WooCommerce account” field is empty.

This happens because when a workflow runs as a subworkflow, n8n sometimes loses the credential link even though it looks fine when you run the node manually.

To fix it, open your subworkflow, click on the get_product node, go to the WooCommerce API field and manually select your credentials from the dropdown even if it looks like it is already set. Then save the workflow.

Do the same for the get_product1 node as well since it has the same warning icon.

After doing that, activate the workflow and test it again from the parent workflow. This should resolve it.

thank you , unpublishing the workflow and reselect the creds then publishing seems to solve the issue