[REQUEST] Better Error Handling

[waleedlatif1]

Is your feature request related to a problem? Please describe.
For many of the tools, we get generic errors back like "___ block failed" but we should do validation on all the required input parameters for a tool/block and ensure that we are giving the user descriptive errors.

Describe the solution you'd like
If the user doesn't provide an API key for a tool, we should tell them "API key is required for block ___" instead of showing a generic error in the console log. This makes the whole debugging flow easier and just increases the usability.

[mo-amir-code]

💡 Proposed Implementation Approaches
We can enhance the validation and error feedback in the following ways:

Inline Validation on Run:
When the user clicks the Run button, validate all required input fields.
If any required field is missing, display an inline error message directly below the respective input.
Additionally, show a general alert such as:
"Please fill in all required fields to run the workflow."

Centralized Validation Before Execution:
During the tool data validation step, check for all required fields.
As soon as a missing required field is detected (e.g., API key), stop further processing and display a clear, descriptive error:
"API key is required to run the workflow."
This approach ensures that users are immediately informed about missing inputs that are critical to execution.

By implementing one or both of these strategies, we can significantly improve error transparency, reduce user frustration, and streamline the debugging process.

Can I start work on this issue?

[emir-karabeg]

@mo-amir-code great suggestion! I’d love to see your implementation! Ping us in Discord or in this thread if you have any questions.

We already have a serialize step that returns some limited errors, but please play around and enhance anything you see regarding error logging back to the console.

[waleedlatif1]

already done