Here is a round-up of features/improvements introduced in the last 2 weeks:
- Database Extractor Configuration Migration Tool
- fixed email activation for new user accounts.
- custom expiration period when creating new personal access token
- The project expiration warning is shown on the overview page only if there are less than 30 days left.
- UI for Mailchimp extractor
On Jun 13, 2016 from 5:50am till 6:20am UTC+2 we encountered issues with DNS that may have led to failure of some running jobs at the time. We are sorry for any inconvenience.
We did a little cleaning and dropped unused or deprecated components:
old Sklik extractor, old Adwords extractor, Instagram extractor, Telfa extractor, Marketo extractor, Elasticsearch extractor and writer, Linkdex extractor, App Annie extractor, Mandrill extractor.
Don't worry if you found yourself missing one of those, we are able to bring them back and have found effectively betters ways to do it ;)
Some of Good Data writer jobs have failed between 22:59 PDT and 23:44 PDT.
It was caused by incident in Keen.io service which Good Data writer uses.
We are sorry for any inconvenience.
UPDATE: this issue has been solved and one shall not encounter the problem described below.
We have encountered problem when running orchestration manually from the orchestration detail page:
error message detail: "Error. [Task 0] Job task is different from orchestration task"
We are working on the fix of the problem which should be released within a short while.
Temporal workaround: if you are experiencing such a problem, you can fix it by resaving the orchestration tasks(Edit Tasks->Save).
All other orchestration features are working normally. We are sorry for any inconvenience.
We have experienced a brief outage of Keboola Connection application and API between 12:42 and 12:45 UTC. Some jobs might have failed with an application exception.
We're sorry for this inconvenience, if not sure what was the cause of any failed job, please contact us atsupport@keboola.com.
Today, 11.2.2016 between 11:50 - 12:50 CET we encountered short outage of our MySQL transformation server which at the time led to fail the running transformations and no new transformations could be started either. The server is now up and everything is running properly. We are sorry for any inconvenience.
Access to component configurations can be now granted to Storage API tokens.
Until now only tokens assigned to administrators or tokens with access to all buckets had access to component configurations.
Running empty transformations bucket will no longer throw an error.
Orchestrations can be now composed and executed by other orchestrations. The nesting level is limited to two levels, and deeper nesting will trigger an error on orchestration execution.
Recent issues with exceed client ids count were resolved.
Jobs were unaccessible between 4:30am–4:31am PST which caused failure of few orchestrations. These were restarted.
UPDATE 6:22am PST
The issue reappeared between 5:48am and 6:09am PST. All failed orchestrations were restarted.
We are sorry for any inconvenience.
Due to networking issues a few orchestrations failed around 5:15 PM PST.
The problem is resolved now, sorry for any inconvenience.