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
Describe the bug
I have the archival connected to S3 bucket, it was working for few months and sudenly I cant find any archived wrkflow from the UI and it keeps loading for a long time after that show me no available archival. But If I check the archivals using tctl command I can find them.
I had the latest version temporal serevr 1.22.7, I thought the issue is from the version, so I upgraded also my server and UI to the latest version and issue still exist
To Reproduce
Steps to reproduce the behavior:
No Idea
Expected behavior
to show me the archived workflows
Screenshots
After loading for 1-2 minutes, it will give me the below message
The text was updated successfully, but these errors were encountered:
when I cleared the S3 bucket, I was able to open again the archival and it was very fast.
So after troubleshooting, I found if your s3 bucket has more than 1k objects like archived workflows then you will face the above issue and it wont work.
I think it is related to the timeout between temporal and s3 and how much fast the temporal get the data from s3. It seems you may need to enhance the streadming data in a better way
Describe the bug
I have the archival connected to S3 bucket, it was working for few months and sudenly I cant find any archived wrkflow from the UI and it keeps loading for a long time after that show me no available archival. But If I check the archivals using tctl command I can find them.
I had the latest version temporal serevr 1.22.7, I thought the issue is from the version, so I upgraded also my server and UI to the latest version and issue still exist
To Reproduce
Steps to reproduce the behavior:
No Idea
Expected behavior
to show me the archived workflows
Screenshots
After loading for 1-2 minutes, it will give me the below message
The text was updated successfully, but these errors were encountered: