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
When you haven't logged into the Console for a certain period of time and try to access the page again, you may encounter the following error message in the Console.
Resources for the function are being restored. (Service: Lambda, Status Code: 502, Request ID: xxxxx-xxx-xxxx-xxxx-xxxxxxxx)
Expected Behavior
No error response.
Current Behavior
Return errors as the following,
Resources for the function are being restored. (Service: Lambda, Status Code: 502, Request ID: xxxxx-xxx-xxxx-xxxx-xxxxxxxx)
Reproduction Steps
If you log out of the CLO Console and do not log in again within 7 days, there is a possibility of encountering this issue when you log back into the Console.
Possible Solution
No response
Additional Information/Context
No response
Solution Version
v2.1.2
AWS Region. e.g., us-east-1
us-east-1
Other information
No response
The text was updated successfully, but these errors were encountered:
This issue might occur due to prolonged inactivity in the Console, resulting in no API calls being made. When users log in again, it could lead to a cold start of Lambda. However, this problem does not affect user functionality. Simply refreshing the page a few times will resolve it once the Lambda functions are back to normal.
Describe the bug
When you haven't logged into the Console for a certain period of time and try to access the page again, you may encounter the following error message in the Console.
Resources for the function are being restored. (Service: Lambda, Status Code: 502, Request ID: xxxxx-xxx-xxxx-xxxx-xxxxxxxx)
Expected Behavior
No error response.
Current Behavior
Return errors as the following,
Resources for the function are being restored. (Service: Lambda, Status Code: 502, Request ID: xxxxx-xxx-xxxx-xxxx-xxxxxxxx)
Reproduction Steps
If you log out of the CLO Console and do not log in again within 7 days, there is a possibility of encountering this issue when you log back into the Console.
Possible Solution
No response
Additional Information/Context
No response
Solution Version
v2.1.2
AWS Region. e.g., us-east-1
us-east-1
Other information
No response
The text was updated successfully, but these errors were encountered: