You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Hive3 . When I run a responder execution as part of workflow I get the following error
The resource you are requesting could not be found
A client error occurred on POST /api/v1/query?name=task-actions :
although the task is successfully executed and the responder in Hive is working. N8N can't get the status of the task because it is pulling a path that is not in the hive api.
This is the response I get when I request the address “.../api/v1/query” in Hive
404 A client error occurred on GET /api/v1/query : Resource not found by Assets controller
To Reproduce
Go to workflow builder
Create Hive3 execute responder node
Add credentials and task id
Select the required responder
Start the node
Expected behavior
N8N successfully obtains responder execution status and does not generate an error
Operating System
Ubuntu 22.04
n8n Version
1.55.3
Node.js Version
v20.15.0
Database
PostgreSQL
Execution mode
main (default)
The text was updated successfully, but these errors were encountered:
There is no public status for our internal tickets at the moment, Looking at this one have you tried manually calling the API just to make sure it is working?
Bug Description
I'm using Hive3 . When I run a responder execution as part of workflow I get the following error
although the task is successfully executed and the responder in Hive is working. N8N can't get the status of the task because it is pulling a path that is not in the hive api.
This is the response I get when I request the address “.../api/v1/query” in Hive
To Reproduce
Expected behavior
N8N successfully obtains responder execution status and does not generate an error
Operating System
Ubuntu 22.04
n8n Version
1.55.3
Node.js Version
v20.15.0
Database
PostgreSQL
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: