aws / aws/amazon-sagemaker-feedback
Data flow exports are failing in Canvas Data Wrangler
- Dominant language
- No language data
- Stars
- 10
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
### Product Version
- [ ] Amazon SageMaker Studio Classic
- [X] Amazon SageMaker Studio
- [ ] Issue is not related to SageMaker Studio
### Issue Description
Data flow exports are failing in Canvas Data Wrangler.
### Expected Behavior
Selecting "Export to Canvas Dataset", or "Export to Amazon S3" from a node in an error free data flow should result in a successful processing job and output written to the corresponding location.
### Observed Behavior
Selecting "Export to Canvas Dataset", or "Export to Amazon S3" results in a failed export with the following error (see attached screenshot):
"_... export has failed. Workflow failed. Canvas can't process your request right now. Try again in a few minutes, or contact your administrator and share the details below to resolve the issue._"
I've tried exporting different data flows and all are failing with this error. This has been an issue since last Friday (9/13/24), and it's also an issue I've experienced previously in the past month. It initially disappeared when the option to disable "Auto job configuration" was removed from the UI.
In addition, if I try to manually configure a SageMaker Processing job, by disabling "Auto job configuration". The jobs fail with a different error:
### Product Category
Data Wrangler
### Feedback Category
Error Handling and Debugging, Reliability and Stability, User Interface
### Other Details
_No response_
Contributor guide
Research direction
Start by reproducing exports from an error-free Data Wrangler flow in Amazon SageMaker Studio using both “Export to Canvas Dataset” and “Export to Amazon S3.” Compare the export failure with the separately reported manually configured SageMaker Processing job failure and review the attached screenshots. Done means both export paths create successful processing jobs and write output to their corresponding locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100