Skip to main content
Nintex Community Menu Bar
Knowledge Base

Seq Error - Responded 401 to robots-manager graphql

  • June 23, 2024
  • 0 replies
  • 37 views
  • Translate

Forum|alt.badge.img+3

Topic

If below error is found in SEQ : “Responded 401 to /robots-manager/graphql”


Related to Nintex Robots manager service application.
Task created manually or started by trigger will remain stuck in queue. If a task is opened that was initiated by any trigger, it will show that Robot is not available:

Inside console Robots will show as available and idle:


Instructions 

To resolve above issue, open Robot config file to check Graphql endpoints for Robot manger and task manager:


URL to check the same is as below:

{FQDN}/unattended/task/isAlive
 

Resulted in error


{FQDN}/unattended/robot/isAlive
{FQDN}/unattended/queue/isAlive

Was giving is alive notification

Open the file:

{Install directory}\Kryon\WatchDog\appsettings.Production.json

Look for the port used for Task management SVC


Try to open:

{FQDN}:50002/tasks-manger/isAlive

If it shows "is alive" notification:


Check if there is a port mismatch under Kryon-upstreams.import under nginx directory as shown in below image:

Port Key looks correct:
 


 Replace 127.0.0.1 with server IP address:


Post saving above changes and Restart Nintex authentication gateway service:


Success!

{FQDN}/unattended/task/isAlive is giving alive notification.

 


Robot started working and task in queue started running :


 

 

 

Did this topic help you find an answer to your question?

0 replies

Be the first to reply!

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings