How to speed up communication with CloverCARE support

Did you come across any issue in CloverETL? In order to have it resolved as quickly as possible, consider attaching the following general information when contacting us. Try to provide all information applicable to your situation.

Define your enviroment

For CloverETL Designer For CloverETL Server
Version of CloverETL Designer Version of CloverETL Server
Does the issue appear in local Designer project? Does the issue appear in local Designer project?
Does the issue appear in remote Server project? Does the issue appear in remote Server project?
Java used with CloverETL (vendor, version) Java used with CloverETL (vendor, version)
OS (vendor, version) OS (vendor, version)
Application server used with CloverETL Server (vendor, version)
Memory settings of CloverETL Server (Xms, Xmx, PermGen)

Describe your issue

Attach a runnable example graph throwing the error plus all files necessary to run it (externalized connection files, metadata files, custom jar files etc.) Delete all sensitive information like passwords from it.
Did the issue appear just once or it appears regularly?
Which steps led to appearance of the issue?
Did the issue appear in previous versions of CloverETL as well?
Run log of the unsuccessful job
Log file all.log of CloverETL Server covering at least the moment of the error appearance. The log is available in <java.io.tmpdir>/cloverlogs/all.log. For example in a default Tomcat installation, the log is placed in <tomcat>/temp/cloverlogs/all.log
Source files