fix(screenshot-capture): add try catch block for processing screenshot

[gabiborlea]

couldn't reproduce the error but it seems that there is an uncaught error when calling that function

[saghul]

I don't think this solves the "browser seems blocked" problem. Catching the exception and logging won't magically remove the pressure.

I think there should be a queue that runs at most X of these jobs concurrently to make sure that even if it takes 3 hours to upload a single image, it would not have tons of them running concurrently.

[gabiborlea]

I don't think this solves the "browser seems blocked" problem. Catching the exception and logging won't magically remove the pressure.

I think there should be a queue that runs at most X of these jobs concurrently to make sure that even if it takes 3 hours to upload a single image, it would not have tons of them running concurrently.

added some sort of a queue

[github-actions[bot]]

This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[saghul]

Is this still relevant Gabi?

[gabiborlea]

I think the endpoint has been change to not return 500 anymore so the change might not be needed here anymore

[saghul]

Alright, let's close for now.