Description
Describe the feature you'd like and why
During the Documentation crawling process, if the requests to supabase fail (for example expired or invalid api tokens) and return a 401, the process should probably interrupt, and show an error that supabase returned a 401 and didn't save anything.
User Impact
Currently, the logs will print out the responses from the requests, so if you know where to look in the logs, you can find that the supabase calls return a 401 'Unauthorized', but it's kind of buried in the logs. The log output does say "Stored {X} chunks for {url}." which is deceiving because nothing was saved in the db. When you go to look at your site-pages table after everything is complete, the table will be empty with no clues as to why.
Implementation Details (optional)
Since the output of the entire process is to have the vectors in the db, if any step along the way prevents anything from being stored, the entire process should stop, return an error, and probably display a toast / message in the front end with details and recommendations for troubleshooting.
Additional context
N/A