Some orchestrations may not have started between 3.7.2014 6:00 AM and 4.7.2014 3:15 AM due to bug in Orchestrator. Please check that your orchestrations have been started.
We apologize for any inconveniences.
Several projects may have experienced errors in data loads described as Csv handling fails during the night and morning. The problem is fixed and should not occur anymore. We apologize for any inconveniences.
GoodData Writer experiences occurring network errors during download of csv files from storage and that cause failures of some load data jobs. We are working on fix. Thanks for patience.
Update: It seems that the network errors ceased. In addition we published a fix which should properly deal with such errors in the future. We apologize for any inconvenience.
We are experiencing problems with one of our server causing fails of some GoodData Writer jobs. They typically end with “Job execution error” message without other explanation. We are working on fix. Thanks for your patience.
Update: The problem should be fixed by now.
We are investigating issue with slow Storage API table imports on some table, some transformations have failed on time import limits.
Our main transformation server (TAPI-A) was down between 8:21pm and 8:27pm PST. We had to restart this server to solve connectivity issues. We tried to find all crashed orchestrations and restart them.
EDIT 8:51pm PST: We’re still having issues with TAPI-A server. Switching all transformations to OVH server.
EDIT 9:45pm PST: The issues persisted on the OVH server. We found a bug in the transformation engine and did a rollback to a previous version. Everything should be operating normally now.
We apologize for this inconvenience, if you find any failed orchestrations, that were not restarted manually, please feel free start them again.
We are experiencing issues with GoodData Writer jobs started between 12:00 and 12:30 CET. We are working on fix. All new jobs created after that time should be processed without problem.
UPDATE: The bug is fixed and all affected jobs have been restarted. Everything should be ok by now. Sorry for any inconvenience.
There was a fatal bug in Redshift transformations from March 2, 7pm PST to March 3, 5am PST. All Redshift transformations were failing, this bug has been fixed and deployed. All affected orchestrations were restarted. We apologize for this inconvenience, you can now proceed with your Redshift transformations.
We are experiencing issues with GoodData writer queue. Jobs are now waiting. We are working on the fix.
UPDATE
Problem is fixed and all jobs are running.
We had to rollback transformation API, during bug in rollback some transformations failed and ended with HTTP error 500.