Improve error handling and logging from GlobalJobPreLoad

[BigRoy]

Is there an existing issue for this?

• I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?

It's often hard to debug Ayon Deadline issues - especially if they're related to either first-time setup or connection issues to the AYON server.

Take for example this log reported here:

• Download report: message.txt

Taking the essence of the logs on connections and errors:

ayon_api.exceptions.ServerError: Connection timed out.
Created local site id "liberal-ivory-sawfish"
>>> Connected to AYON server http://ayon
...
!!! Got invalid credentials.
Could not connect to AYON server 'http://ayon'.
!!! Please use 'AYON_SERVER_URL' and 'AYON_API_KEY' environment variables to specify valid server url and api key for headless mode.
RuntimeError: Failed to run AYON process to extract environments.
!!! Injection failed.

These look like two errors at once.

1. A server timeout. -- Then it DID connect (maybe that's an automatic "retry"?)
2. Got invalid credentials.

But first and foremost - it's hard to identify WHAT went wrong?

How would you imagine the implementation of the feature?

If the connection times out, but then goes to retry - it should report nicely:

• Connecting to x
• Failed to connect. Retrying 1...
• Failed to connect. Retrying 2...
• Connection succeeded
• OR Connection timed out. Unable to connect to server: x. Please confirm your server URL is correct and your worker has access to the address.

---

And of course we shouldn't be ambiguous about what failed in this case (if we can identify it?)

Are there any labels you wish to add?

• I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

Write a FAQ for issues that often occur for AYON Deadline Integration and always point users there if they are having issues.

Additional context:

No response