In Executions,HTTP Request node display issues: credentials for ‘bearer auth’ are not set,but my workflow executes successfully.So it seems to be a display issue?I’ve tried to edit node and publish the workflow again,but it still exists.How to solve it?
This is a display-only issue, not an actual execution problem. Your workflow is running correctly, the credential warning you see in the execution view is a known UI rendering quirk in n8n.
What’s happening: when the execution detail view renders the HTTP Request node, it checks whether credentials are “set” based on the node configuration snapshot, but it sometimes fails to resolve credential references properly in the display layer. The actual execution engine handles it fine (which is why your workflow succeeds).
A few things you can try:
Re-select the credential in the HTTP Request node config (open it, pick the same Bearer Auth credential again from the dropdown, then save). This sometimes refreshes the internal reference.
Delete and re-add the HTTP Request node with the same settings. This forces n8n to create a fresh node configuration that the display layer can resolve.
Update n8n if you’re not on the latest patch. Display bugs like this get fixed regularly in minor releases. You’re on 2.10.4, check if there’s a newer patch.
If the workflow keeps executing successfully, this is purely cosmetic and you can safely ignore it. But yeah, it’s annoying to see that red warning when nothing is actually broken.
Thanks,I tried Re-select the credential in my description.I tried Delete and re-add the HTTP Request node serveral mins ago,it didn’t work.
As for Update,I update n8n to 2.11.2(current stable version said in official documents),this problem still exist.
Hi, if the workflow runs successfully, it’s probably just a UI warning. Sometimes this appears if bearer Auth was changed or not fully saved.
Try opening the HTTP Request node, reselect the credential or set Authentication to “none”. Then save and run again
Try your method,still the same.
But i notice one thing,there is no save button on the editor surface of workflow near the publish button(2.10.4 and 2.11.2 now).It save my workflows automatically.It’s different from the n8n UI I deployed in ubuntu a month ago(i save my workflow through save button,version may be 2.1.5 around).
Automatical save work correctly,i am not sure whether automatical save is involved,or something may happen.
I confirm the version is 2.1.5 for n8n deployed in ubuntu.Then I change current version 2.11.2 to 2.1.5.This problem do no exist.So this problem start to appear between 2.1.5 and 2.11.2.I will keep 2.1.5 until I need to update to use new features.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
