Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish: Should be able to view a detailed error message at the top of the notebook in the "VIEW RESULT" section for the failed scheduled notebooks instead of None or general message like "Internal error occurred for the current attempt."
How this might work: Help the user to quickly identify and resolve the issue instead of manually scrolling through the "VIEW LOGS" page. , which leads to a delay in data delivery and impacting stakeholders.
If applicable, reasons why alternative solutions are not sufficient: NA
Other information (workarounds you have tried, documentation consulted, etc):
This lack of clear error messaging has caused two major problems:
a)Failed Scheduled Runs: We rely on scheduled Vertex AI notebooks to automate data updates, especially during holidays. Recently, a scheduled notebook failed with the general message "Internal error occurred for the current attempt." The lack of a clear error message in "VIEW RESULT" prevented us from quickly identifying and resolving the issue, leading to a delay in data delivery and impacting stakeholders.
b)Inaccessible Logs for Monthly Schedules: We have many monthly scheduled notebooks. Due to other priorities, we don't monitor these daily. However, we've encountered situations where "VIEW LOGS" is no longer available for these monthly runs, presumably due to log retention policies. Again, clear error messages in "VIEW RESULT" would be invaluable in these cases, as they would persist regardless of log availability.