Command History is Not Recorded After Reaching Timeout Period for Cloud CLI

Support
1

In Bluescape, after reaching the timeout period for the Cloud CLI, attempt another query. Valid queries will return results with ‘ReferenceError: Can’t find variable: timeout’ appended to the end. Next, view history and see the command is not recorded.

Steps to reproduce

  1. Using Cloud CLI, enter some commands, valid or invalid
  2. Wait 30 minutes
  3. Enter another command
  4. View “ReferenceError: Can’t find variable: timeout” OR no error
  5. Enter ‘history’ command OR keyboard up previous commands
  6. View command after timeout not in list

Expected result

History is recorded as normal and login is refreshed. Or, prompt returns ‘need to login again’ and commands fail.

Observed result

History is not recorded and a timeout error is shown or no timeout error is shown. Commands work.

Our team is working towards a solution. We encourage you to follow this topic, as information is subject to change.

If you are experiencing this issue, please react to this topic and help our product team understand the scope of impact on our members. Plus 1

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.