When users submit jobs via Seqera Cloud (particularly with Google Batch executions), if there are underlying API request errors or IAM permission issues (e.g., request is denied or returns 403 errors), the Platform currently surfaces a generic message:

This generic response is uninformative and forces users to reach out to Support to understand what went wrong. To enhance the user experience and reduce unnecessary support inquiries, we need to improve how these errors are surfaced to users. Infrastructure and DevOps teams at larger organizations also often need access to these error details to debug permission issues and misconfigurations on their end. Lack of clear error messages slows down troubleshooting and increases dependency on Seqera support.

Instead of a generic error, display something like and potentially the response as well: