Help improve AWS Support Official channel in re:Post and share your experience - complete a quick three-question survey to earn a re:Post badge!
AWS Blu Age L3 Workshop - the entire project in Codebase and Transformation Center gets lost intermittently
I've been working on AWS Blu Age Level 3 Self-Paced Troubleshooting Workshop for about a month since I got certified as L2.
It's been very difficult for me to dedicate myself to the above and finish it within a couple of days.
When I returned to AWS Blu Insights after a couple of day absense, I observed the entire work that I've done in Codebase and Transformation Center are somehow lost.
As I don't know how to recover from the loss, I had to do them again all over from the beginning.
Now this is the second time of the disastrous loss.
Would you please advise me how to stop losing the project from Codebase and Transformation Center?
Would you please recover my recent project to Codebase and Transformation Center?
If it is done automaticcaly somehow by the organizer or administrator of AWS Blu Insights, would you please ask them to stop removing my project until I complete the L3 presentation?
- Newest
- Most votes
- Most comments
When I switched the region to eu-central-1 region: Frankfurt at Setup environment, I didn't notice that my project in AWS Blu Insights stayed in the previous region before switching. After I returned to the original region and launced AWS Blu Insights again, I see my project staying there. Accordingly, the problem was solved by myself. Thanks.
I understand your frustration with losing your progress in the AWS Blu Age Level 3 Self-Paced Troubleshooting Workshop. This is indeed a challenging situation, especially when you're dedicating time over an extended period to complete the workshop.
Unfortunately, there isn't a built-in automatic recovery mechanism for lost projects in the Codebase and Transformation Center of AWS Blu Insights. The loss of your project is not a standard occurrence and is not typically done automatically by organizers or administrators.
To prevent losing your project in the future, consider these steps:
-
Save your progress frequently: Make sure to save your work regularly within the Blu Insights platform.
-
Export your project: If possible, export your project or key components at the end of each session. This will allow you to reimport if needed.
-
Take screenshots: Capture screenshots of important configurations or progress milestones.
-
Document your steps: Keep a separate log of the steps you've completed and any important decisions made during the workshop.
-
Check session timeouts: Ensure you're not being logged out due to inactivity. Always log out properly when you finish a session.
-
Verify your internet connection: A stable internet connection is crucial to prevent data loss during saves.
As for recovering your recent project, I apologize, but I don't have the ability to directly recover or restore your lost work in the AWS Blu Insights platform.
Given that this is the second time you've experienced this issue, I strongly recommend reaching out to AWS Blu Age support or the workshop organizers directly. Explain your situation, including the repeated loss of your project. They may be able to:
- Investigate the cause of the data loss
- Provide specific guidance on preventing future occurrences
- Possibly restore your project from a backup (if available)
- Offer alternatives or accommodations to help you complete the workshop
Remember, the workshop organizers want you to succeed, so don't hesitate to ask for their assistance with this technical issue. They may also be able to provide insights into any known issues with the platform or offer workarounds to ensure you can complete your L3 certification.
Sources
Blu age L3 Execution/backend/import project | AWS re:Post
AWS Blu Age Level 3 Self-Paced Troubleshooting Workshop - Codebase transformation - Transform Error | AWS re:Post
L3 Troubleshooting Workshop- Fatal errors when transforming project scope | AWS re:Post
I'm not happy with such solution in general at all. I'm asking for recovery and preventing action for specific problem happened to me.