Hi Zheng,

That's very unfortunate that the authentication status moves to 'Authentication Error' after some time.
It should not be required to recreate your element every time, let's try to find the root casue.

It should only move to this authentication error state in the following cases:

• The authentication login request failes at that given point in time
• The authentication token that is being used after a successful login has expired and further API request are then failing.
• The given user doesn't have enough permissions to request all the data from the chassis. Certain API responses would then return an authentication failure response as the permissions for the given user aren't high enough.

My suspicion would be that the given credentials don't have enough permission to request everything. Would it be possible to verify if the given user has all permissions? Or try with a different username/password?

There are a few other things that we can further investigate to get to the bottom of this:

• Would there be any exceptions visibile in the element log file? If so, which one(s)?
• Under the General page, there is a pagebutton/subpage for 'HTTP Communication...'. Would it be possible to enable the Logging state at the top of this page? This stores the request and responses in the table for a clearer overview. It would be useful to know the first row which is NOT having a 'OK' value for the column 'Response Status'. This failing API request might be the reason for the Authentication error status.
  

Let us know if could verify the user permission, element log file or the failing API command from the HTTP Sessions table.

Kind regards,
Robin