tag:status.keboola.com,2013:/posts Keboola Status 2018-02-19T17:10:29Z Keboola Connection "Data Framework" tag:status.keboola.com,2013:Post/1250008 2018-02-19T17:10:29Z 2018-02-19T17:10:29Z Week in Review -- February 19, 2018

New components

Bug fixes and smaller improvements

  • Bug fix in Currency extractor - exchange rates for Danish Krone (DKK) and Icelandic Krona (ISK) were not updated for some time because of a bug in its configuration.
  • Snowflake extractor now offers views in the tables list too.
Jakub Matějka
tag:status.keboola.com,2013:Post/1243850 2018-02-13T15:38:19Z 2018-02-13T15:38:20Z Time Travel Restore

Snowflake has a wonderful feature that they call Time Travel.  It allows you to replicate your table from its state in the past.  We're happy to announce initial support for this great feature in Keboola Connection. 

To begin with, every project with a Snowflake backend has been set to retain data history for 7days. That means that you can restore a table to how it existed at any point within the last week.  It is possible to increase the data history retention period, so if you're interested in doing that please let us know by using the support button in your project

We've added this restoration method to the snapshots tab in the storage console:

Restoring a table is very simple, just use the calendar to pick the date and time, give the new table a name, and choose which bucket to put it in.

We plan on extending the use of this feature to be able to use time travel replicas as an input option for transformations and to create a "Storage Trash".  

Happy travelling!

tag:status.keboola.com,2013:Post/1246382 2018-02-12T10:28:18Z 2018-02-12T10:28:18Z Google BigQuery Extractor failures

There were Google BigQuery Extractor  jobs failures between 10th  and 12th February. It was caused by internal platform changes, the issue is resolved now. We are sorry for inconvenience.

tag:status.keboola.com,2013:Post/1244928 2018-02-12T07:20:59Z 2018-02-12T07:20:59Z Week in Review -- February 12, 2018

New Components

  • Google Trends extractor: this component, developed by Leo Chan (cleojanten@hotmail.com), allows to extract search trends for given keywords in a specified region.


Indexed columns

With the deprecation/removal of the MySQL backend, we deprecated indexed columns because there is no more use for them. You can search/filter through any column now without the need to mark it as indexed.

The following attributes will be removed from manifest files by the end of March 2018:

  • indexed_columns – with the deprecation of the MySQL backend, there is no need to define indexes.
  • rows_count and data_size_bytes – these values are not (and never were) in sync with the input table data and are useless.
  • attributes – table attributes are replaced by table metadata.
  • is_alias – this is something that has nothing to do with the exported data.


  • The Developer portal is now available under a new URL: components.keboola.com (instead of apps.keboola.com). The main reason is that we used the word application in two meanings, and that was confusing. For example, there were applications of type Extractor but also applications of type Application. From now on, everything is a Component. Components are of four types: Extractors (loading data from somewhere), Writers (writing data somewhere), Applications (manipulating data), and Processors (data processing helpers).
tag:status.keboola.com,2013:Post/1239746 2018-02-01T15:27:10Z 2018-02-01T15:27:11Z Week in Review -- January 30, 2018

Plantyst Extractor

To those who are collecting data from productions machines to Plantyst, you can employ new extractor made by BizzTreat and start doing complex data analysis.

Stories.BI writer

You can automatically push data to Stories.bi and get automatic insights instead of crunching business data by hand.

Updated Components

  • Sklik extractor has new variable accountID
  • YouTube extractor has new version. It is based on Generic Extractor. Old extractor will be deprecated on March 1, 2018
  • Snowflake extractor is now a bit faster and has better error handling
  • Geneea NLP App is now available in EU region
  • BingAds extractor is now available in EU region
  • Facebook extractor with new Page Tokens can newly fetch Page Reviews
  • Twitter extractor is now available in EU region
  • Snowflake and Redshift writers has fixed eventual columns mismatch.

Minor Improvements

  • Quick search in component list was improved - it has better accuracy
  • Component name can be finally submitted by pressing ENTER

Petr Šimeček
tag:status.keboola.com,2013:Post/1236293 2018-01-25T00:01:03Z 2018-01-25T00:01:03Z Week in Review -- January 22, 2018

Linked/Source Buckets

From now, you'll be able to find source/linked buckets information in Storage section in Keboola Connection. This is very helpful when you need to find out which projects are using (linking) your shared bucket. Also, vice versa, which bucket is the source for your bucket.

MFA required also for Google Login

If you have MFA (Multi-factor Authentication) enabled, a confirmation code is required if you use "Login with Google" functionality. Please contact us if you have problems with login.

Facebok Extractor uses page access token for page/posts insights retrieval

Due to breaking changes recently introduced by Facebok API our facebook extractor is updated so it uses page access token for page or posts insights retrieval instead of user access token. This leads to slower extraction if more pages are included in a query. User access token is still used for other data retrieval such as feed, likes, comments. Moreover, this change does not affect facebook ads extractor. 


  • We slightly updated UI for the recently published Tokens page


  • Project Power consumption is shown only for the current + 2 previous months. This is only a temporary limitation.  It will soon be solved and return to showing you more data

Vladimír Kriška
tag:status.keboola.com,2013:Post/1235407 2018-01-21T09:50:38Z 2018-01-30T12:03:24Z Snowflake Outage in US Region

There was a short Snowflake outage between 10:30 and 10:35 CEST (09:30am and 09:35am UTC) in US region.

  • Sandboxes might have lost their data and worksheets
  • Transformation jobs might have finished with an error
  • Async data loads and exports were unaffected

We're investigating the impact and root cause and will update this post as soon as we know more. Snowflake is now back fully operational.

UPDATE Jan 30 2018: Snowflake released their RCA.

Ondrej Hlavacek
tag:status.keboola.com,2013:Post/1228326 2018-01-10T13:29:46Z 2018-01-10T13:29:46Z New UI section for API Tokens

We are glad to introduce a new UI for Storage Api Tokens that can be now found under the Users & Settings section. We will be removing the old one found under Storage section. The new UI covers the same functionality as the old one.

As a security measure, the token itself will not be shown anymore, only once after its creation. The only way to see an existing token in the UI is to send it via email (temporary link to token is sent) or refresh it and get a new token string. On the backend, the token can still be seen in the response from the tokens list api call but will be removed in the near future.

tag:status.keboola.com,2013:Post/1229093 2018-01-10T07:54:54Z 2018-01-11T08:08:24Z Week in Review -- January 9, 2018

You haven't heard from us for a while. We're sorry. Here's what's new.

New Components

Updated Components

Minor Improvements

  • SSL configuration of all database extractors is on the same page with credentials and the SSH tunnel configuration
  • Database extractors give a warning if your connection is invalid
  • Apify Extractor accepts a list of urls from a table in Storage
  • New part about ad-hoc data exploration in Jupyter was added to the tutorial on Ad-hoc Data Analysis


  • Database extractors automatically changes table names to lowercase
  • Fixed a bug affecting non-incremental import of sliced tables in the BigQuery and Snowflake extractors 


Our developers have published 2 blog posts

Community News

Ondrej Hlavacek
tag:status.keboola.com,2013:Post/1228744 2018-01-08T22:09:15Z 2018-01-08T22:09:15Z Failed Jobs

Today (8.1.) at 20:05 - 21:56 UTC a number of jobs failed with internal or encryption error. This was caused by a bug affecting OAuth configurations. We have reverted the internal release. We do apologize for this enormous mess up.

tag:status.keboola.com,2013:Post/1224140 2017-12-31T10:49:53Z 2018-01-02T10:49:43Z Year 2017 in Review

Since most of us are enjoying the winter holiday, the usual Week in Review would be half-empty. It's perhaps time to review the year with the benefit of hindsight. A lot of stuff happened last year which is easily lost in the daily commotion, so let's have a little recap.

The big things

  • Keboola Connection in EU region — Although this might not look exactly revolutionary, it required immense amount of work to make it so our backend is not tied to a specific region any more. This of course opens doors to other regions, which are going to be much easier to do.
  • Developer Portal — This allows anyone to create and deploy applications in Keboola Connection. Hosting of Docker images, automated deployment and testing integration — all inclusive.
  • Big files support and other performance improvements — We all have big data, don't we? There were a number of limitations in several places which didn't allow processing of files larger than 2GB or 5GB. Though there are new limits now (around 100GB), it's much harder to hit them. A lot of other performance improvements were achieved, among those the recent up to 80% speedup in workspace load is worth bragging about.
  • Component Dockerization — This is a ton of completely invisible work which has no immediate impact on you. Once we are done with this, we'll be able to rework job processing stuff and offer super flexible projects (ever wanted long running jobs? or jobs requiring XXX GBs of RAM?). There is still a lot to do, but we're not dawdling.
  • Shared buckets — Although they are not perfect, they hugely simplify sharing things in larger organizations.
  • Processors — Quite a hidden nerdy feature which is slowly making it into production. This, together with Developer portal opens the door for simplified implementations (especially in extractors) of those "Oh, it's perfect, I just need to convert this one little thing ...".
  • Trash of deleted configurations — A lifesaver for many.
  • RStudio and Jupyter Sandboxes — Do they count as a big thing too?
  • New database extractors — The database extractors were greatly simplified.  You no longer need to remember your database schema, and can make your configuration in just a couple of clicks.
  • UI/UX improvements — No shocking things happened (yet?).  but we certainly put much more focus on this area throughout the year. There are a various new features (markdown descriptions, merging table slices, finer input mapping granularity). But we are also putting a lot of effort in unifying the look and feel of different Keboola Connection parts and smoothing the flow. Hopefully this makes Keboola Connection more pleasurable to work with.

Security improvements

We're keeping an eye over security all the time, and constantly improving. To name a few things:

  • Project Access Approval
  • New Google Sign-in
  • CSP (Content Security Policy) used in entire Keboola Connection
  • Better secured Keboola Connection cookies and sessions
  • Display of all active account sessions

New components

There were literally a ton of new and updated components. Ok, maybe not a ton, but definitely a lot. To name a few:

  • Facebook Extractor, Facebook Ads Extractor, Azor Extractor, Snowflake DB Extractor, BigQuery Extractor, Papertrail Extractor, Dropbox extractor, Pipedrive extractor, CJAffiliate extractor, Dark Sky Extractor
  • GeoIP application, What3words Application, Data Health Application
  • SAS Writer, Google BigQuery Writer, GoogleSheets Writer, Snowflake Database Writer, Qlik writer, Looker writer, Salesforce Analytics Cloud Writer
  • Dozens of other connections thanks to Generic Extractor.

What's next?

  • We are working on replacing the Storage Console as the most ancient part of Keboola Connection UI. This is big, so we'll replace it in parts, but it's already in the works.
  • New GoodData Writer is being made. We want to get rid of its "special" behavior and make it a standard writer. Some of the not-exactly-writery features will go into separate tools.
  • New Pigeon "extractor" is in progress. Again, this is an old component with quirky behavior so it has to be replaced with something reliable.
  • Also a new S3 extractor is waiting behind the door. This will be in many ways a conceptually different extractor taking advantage of processors and having configurations organized in a different way.
  • We're working on making it easier to learn Keboola Connection. It's not quite finished yet, but we definitely want to make life easier for new users.
  • Removing MySQL backend. It's been there a long time and it's sad to see it go. Actually, no it isn't. We'll throw a party when it's gone for good.
  • Database writers are going to get a larger update.

And beside that?

Life is a bitch, so we can't make promises, but:

  • Better managed wish list is something both you and we wish for.
  • RStudio and Jupyter Sandbox have many improvements in queue.
  • We have quite a few (almost revolutionary) ideas about Input mapping.
  • Shared credentials (need three configurations connecting to the same database server?) would make a lot of situations easier to handle.
  • Transformations are going to get simplified (no phases, no dependencies, just transformations).
  • We'd like to support even bigger data (no big is too big), so thanks everyone for pushing the limits.
  • Orchestrator needs quite a few updates and so does Generic Extractor

We hope we meet those and many other goals but that's all for now. 

We wish you all a very happy and successful New Year.

tag:status.keboola.com,2013:Post/1218292 2017-12-18T08:12:57Z 2017-12-18T08:41:40Z Slower job processing

We're experiencing slower Docker components jobs processing, many jobs stalled in waiting state. Finding the root cause, hopefully we'll be back online soon.

UPDATE 9:40 AM CET: All operations are back to normal, the stalled jobs were caused by a misbehaving Redshift cluster. We're going to investigate the root cause. 

We're very sorry for this inconvenience.

Ondrej Hlavacek
tag:status.keboola.com,2013:Post/1209398 2017-12-04T08:55:02Z 2017-12-04T08:55:02Z Week in Review -- November 30, 2017

Database extractors

After recent announcement of new database extractors we are bringing other improvements to these extractors.

  • By default the new bucket is created for each extractor configuration. Previously extractor configurations were sharing one bucket which led to collisions.
  • You can reload the list of tables fetched from database. It is useful when you are tuning credentials permissions or you have just added some tables to the database. 
  • Primary key is now validated against table created in storage. Warning is thrown if the configured key is different than the key defined on the table.

Generic extractor

The new ignoreErrors option was introduced. This option allows you to force Generic Extractor to ignore certain extraction errors.  Read more in documentation.


  • Google Drive Writer in append mode was overwriting rows instead of appending new rows under some circumstances
  • Google Big Query extractor was ignoring files exported to multiple slices
  • Tableau Writer is now available in the EU region

Martin Halamíček
tag:status.keboola.com,2013:Post/1206565 2017-11-22T08:44:21Z 2017-11-22T08:44:21Z New version of AdWords Extractor

We have just released a new version of AdWords Extractor. It works with AdWords API v201710 (see the Release notes) and you no longer need your own developer token to use it.

The previous version of the extractor is deprecated and you can use our migration tool which will migrate your AWQL queries. However, you have to reauthorize the extractor and give it access to your AdWords data again. The previous version uses AdWords API v201705 which will be switched off on 28 March 2018.

Jakub Matějka
tag:status.keboola.com,2013:Post/1206550 2017-11-21T12:50:06Z 2017-11-21T12:50:06Z Week in Review -- November 21, 2017

New Features

  • There is a new extractor for what3words service (https://what3words.com/)


  • Configuration of MySQL Extractor allows parameter database to be optional
  • Loading data to Storage Workspace allows renaming of columns
  • Configuration errors from DarkSky Extractor are properly marked as user errors
  • Unified incremental load settings for all database writers
Jakub Matějka
tag:status.keboola.com,2013:Post/1206518 2017-11-21T08:36:23Z 2017-11-21T10:40:54Z Job Failures Tuesday, November 21, 2017

We have been experiencing temporary technical difficulties today around 9:15 AM CET and 9:20 AM CET.

Some component jobs may have failed as a result. We're investigating the issue and post an update when the root cause is found.

UPDATE 11:35 AM CET Jobs storage was temporarily unavailable for about two minutes. Jobs scheduling wasn't affected and running jobs were waiting until storage came up again so these jobs weren't affected. Unfortunately few orchestrations have failed, we'll do step to prevent this in the future.

Ondrej Hlavacek
tag:status.keboola.com,2013:Post/1206042 2017-11-18T16:00:08Z 2017-11-18T16:00:08Z Job Failures Saturday, November 18, 2017 We have been experiencing temporary technical difficulties today around 3:00 AM CET and 4:00 PM CET.

Some component jobs may have failed as a result.  We have identified and fixed the issue. All systems have returned to normal operations and all jobs are now being processed normally.]]>
tag:status.keboola.com,2013:Post/1205204 2017-11-14T16:41:33Z 2017-11-14T16:41:33Z Google Analytics Extractor - Custom Authorization

Recently we have been hitting quota limits of the Google Analytics API with our extractor. As these limits are shared between all users of the extractor, we decided to add a new authorization option - Custom Authorization.

With Custom Authorization, you can provide your own API keys for the Google Analytics extractor, so you will have your own quota limits. This way you can monitor these limits as you need, and other users won't be affected.

Please check out our step-by-step guide on how to set up Custom Authorization in the Google Analytics Extactor.

In case of any problems or questions, please contact us on support@keboola.com.

Miroslav Čillík
tag:status.keboola.com,2013:Post/1203700 2017-11-14T08:59:53Z 2017-11-15T05:45:45Z Developer Portal

As part of our effort to make Keboola Connection an open platform we would like to announce the availability of the Keboola Developer Portal - https://apps.keboola.com/. Some of you may already be aware that it is possible to modify applications in KBC through the Developer Portal API. Now we are adding an application to the API so that you can get things done more easily.

The Keboola Developer Portal is a completely separate application from Keboola Connection. It is region-less because it has no access to customer projects. The Developer Portal provides an authoritative list of KBC applications for each region. Each Keboola Connection stack reads this list regularly. As usual in Keboola, the Developer Portal is done in an API first approach, so everything that the application does can be done programmatically too.

What does the Developer Portal do?

  • It allows users registered to vendors to create and modify applications in KBC without Keboola Tech support.
  • It provides service accounts for automating deployment and testing.
  • It provides Docker AWS ECR repositories for applications (thus avoiding Quay and Dockerhub issues).
  • It provides an authoritative list of publicly available approved applications.

Anyone can sign up for the Developer Portal. However until you join a vendor or create a new one, you will not be able to do anything. Both creating and joining a vendor must be approved. Joining a vendor must be approved by the vendor administrator, and creating a vendor must be approved by Keboola Tech. Once a member of a vendor, you can modify and add new applications to that vendor. There's no need to fill a checklist and go through our support. When you create an application, it becomes immediately available for you to use. Using the Developer Portal, you can also set up automated deployment for your application.

Keboola Tech still has some things to do:

  • approve new vendors
  • change some controlled properties of an application (e.g. memory limit)
  • approve a new application before it can become public

Next steps:

  • We still have a long list of things to be done on the Developer Portal, so we consider it as beta quality at the moment.
  • We are soon going to hold a developer meet-up in the Czech Republic where we’d like to hear about your experience developing applications for KBC (in January probably).
  • If you have previously used the Developer Portal API, we encourage you to try the application. If you are having trouble joining your vendor, please contact us on support (there may be some friction depending on how your account was created).
  • If you have created complex applications using Custom Science, go ahead and check the Developer Portal, it may now be more convenient to turn them into full applications.
  • If you have never created an application for Keboola Connection, we highly encourage you to try it - it's much easier now. In fact a component can be created from scratch in an hour.


tag:status.keboola.com,2013:Post/1202204 2017-11-13T19:46:20Z 2017-11-13T19:46:20Z Deprecating MySQL Storage and Transformations

Support for MySQL in Keboola Connection is coming to its end. Here's what will happen.

Effective immediately

  • New projects and projects without existing MySQL transformations will not be able to create new MySQL transformations.

MySQL Storage Backend (supported until January 2018)

  • The default storage backend for all projects is immediately switched from MySQL to Snowflake.
  • All MySQL buckets in all projects will be migrated to Snowflake in January 2018. This will not affect any operations, only a short maintenance on the project will be required.
  • No changes in the project are required.
  • You can apply for a sooner migration at support@keboola.com.

MySQL Transformations (supported until April 2018)

  • Your existing MySQL transformations will need to be migrated to Snowflake by the end of April 2018.
  • If you need any help migrating your MySQL transformations, contact support@keboola.com.

These steps will allow us to deprecate a piece of the legacy infrastructure and focus on the state of the art technologies. The Snowflake storage backend and transformations have significant performance and scaling benefits, so your projects will run faster than on MySQL without any extra charge.

Ondrej Hlavacek
tag:status.keboola.com,2013:Post/1204967 2017-11-13T15:09:25Z 2017-11-13T16:00:57Z Week in Review -- November 13, 2017

New Features

  • We are pleased to announce a significant speed boost to Snowflake load to workspace (also speeding up Input Mapping inTransformations). For tables with primary keys the speed difference is up to 80%.
  • We have also simplified our database extractors, as we mentioned here last week.
  • Fixed CSV Import. The component generates meta-data now.

Minor Imporvements

  • We have updated our Terms and Conditions.
    Per section 14.3 of our Master Software Subscription Agreement, we would like to notify you of a change to the Agreement and its new version released November 10th. The purpose of this change was to provide further protection to Client Data and to comply with requirements of some third party providers (namely Google). We do not consider this change to be a material change, however we are obliged to provide you with this notification. There is no action required from you in relation to this change if you accept it. We are setting out the original and revised language for your review below. Please do not hesitate to contact us with any questions or concerns at legal@keboola.com.

    Original (version from March 16th, 2016):
    6.7.1. Permitted Use of Client Data. Keboola will only use and will cause all Affiliates and Keboola employees, agents, subcontractors and representatives to only use Client Data for purposes of performing the Services. Keboola shall follow Client instructions when processing Client Data and will not use Client Data other than as authorized by this Agreement. 

    Updated (version dated November 10th, 2017):
    6.7.1. Permitted Use of Client Data. Keboola will only use and will cause all Affiliates and Keboola employees, agents, subcontractors and representatives to only use Client Data for purposes of performing the Services. Keboola shall follow Client instructions when processing Client Data and will not use Client Data other than as authorized by this Agreement. Client Data which Keboola downloads (with permission granted by Client during component configuration) from Google, Facebook, Twitter or other third party APIs ("Third Party Data") are stored and handled the same as Client Data under this Agreement. Third Party Data will not be shared anywhere (it remains stored securely on Keboola systems) until Client decides to share that data (for example, by configuring Data writer to Client or third party systems). Client can delete all Third Party Data and data source configurations from Keboola storage anytime. This section shall be read along side with and be subject to the provisions of sections 6.9 (Retention and Deletion) and 6.10 (Compliance with Law) of this Agreement.
tag:status.keboola.com,2013:Post/1202446 2017-11-10T08:54:20Z 2017-11-10T08:54:21Z New Database Extractors

We're very pleased to announce the arrival of simplified database extractors.  (Available for MySQL, MSSQL, PGSQL, Redshift, Snowflake, Oracle and IBM DB2)

Configuring the new extractors can not be any easier.  All you need to do is select the tables you want to import and ... that's it! 

You can, of course, choose which columns you want to import, whether it will be incremental or not, and decide where the output should be, but the defaults are usually sufficient.   
Also, have no fear, you can still write advanced queries for your extractor if that's what you need.

If you run into any problems with the new extractors or require any assistance, please don't hesitate to ask at support@keboola.com.


tag:status.keboola.com,2013:Post/1203885 2017-11-08T12:07:59Z 2017-11-08T12:07:59Z Deprecated Facebook Ads API v2.9

Facebook is deprecating Marketing API v2.9 on Monday, November 13, 2017 thus any api call to v2.9 will fail with error.

The latest version is now v2.10.

The migration should only require changing the api-version parameter in all existing configurations of our Facebook Ads Extractor. However, since there may be some breaking changes, we strongly recommend to change the api-version in your configurations manually, review any possible changes and take the appropriate actions.  For more details on the new version, please read Marketing API Changes in v2.10 in the Facebook API Changelog.

Possible breaking change might be renaming of action_link_click_destination breakdown types as follows:

  • app_store_clicks => click_to_app_store
  • deeplink_clicks => click_to_app_deeplink
  • website_clicks => click_to_website

In other Facebook news, they have announced version v2.11 of Facebook Graph API and Facebook Marketing API, for more info read changelog here.

tag:status.keboola.com,2013:Post/1203612 2017-11-06T15:53:41Z 2017-11-09T06:25:48Z Week in Review -- November 6, 2017

New Features

  • Finer granularity in all input mappings. The Days parameter was renamed to Changed in last and you can set the interval of changed data to as short as 10 minutes. Please note, that combining a legacy Days value with a new Changed in last is not allowed (eg. in a transformation chain, where the same table gets imported multiple times, all input mappings have to use the same filter type).

Minor Improvements

  • All new transformations come with a predefined boilerplate that will help you at the start. It is especially useful for Python and R transformations.
  • Sliced tables in Storage console (eg. exports from a Snowflake backend) are now merged when downloaded.
  • Database extractors display the name of the query that failed in their error messages.

Updated Components

  • Oracle DB Extractor and Writer are now available in the EU region.


  • Input Mapping modal has autofocus in the Source field when opened.
Ondrej Hlavacek
tag:status.keboola.com,2013:Post/1202980 2017-11-03T10:25:38Z 2017-11-03T10:25:39Z End of life of Keboola Academy

All things have to come to an end and Keboola Academy’s GoodData training is no exception. But don’t mourn, we are working hard on a new education program. Its main focus will be Keboola Connection.

Keboola Academy courses will be available for purchase until December 31, 2017. After that, you won’t be able to purchase new courses, but you’ll still be able to access your already purchased courses for another two months. Courses will be shut down completely on February 28, 2018.

If you have any questions, please contact us via support@keboola.com.

Miroslav Čillík
tag:status.keboola.com,2013:Post/1201149 2017-10-27T07:23:17Z 2017-10-27T07:23:17Z Week in Review -- October 20 and 27, 2017

New Applications

Dark Sky Extractor

Dark Sky is the new name for the old Forecast.io service. So we have prepared a new extractor for it.  It allows you to look up the weather anywhere on the globe. You can use our migration tool to migrate your existing configurations from the deprecated Forecast.io extractor.

For more information, please see our documentation.

Currency Extractor in EU region

This extractor is now also available in the EU version of Keboola Connection.


  • Dropbox Writer now allows you to specify a custom destination folder name for uploaded data.
  • We have added the ability to configure your own OAuth credentials.  We did this because we are still waiting for quota limits increase for the Google Analytics API for our Google Analytics Extractor.  So now your extractor can run under independent quotas.
  • Tableau Writer now uses the new version of Google Drive and Dropbox Writers to upload data to Tableau.
  • Removed 8 kB script size limit in Rstudio/Jupyter sandboxes
  • Improved handling errors in Rstudion/Jupyter sandboxes. Invalid package names will now throw an error with an explanation instead of an application error.
  • Read-only bucket credentials to your Redshift backend are now deprecated. See this more detailed post about accessing your data since April 18, 2018.


  • Table import events in the Storage panel once again have a link to the imported file.


Unfortunately on Sunday we had some problems with our storage for KBC Events, which delayed execution of jobs.  We apologize for any inconvenience that may have caused.

Erik Žigo
tag:status.keboola.com,2013:Post/1200056 2017-10-22T11:08:21Z 2017-10-22T12:13:35Z Job Failures Sunday, October 22, 2017

We have been experiencing temporary technical difficulties today since this morning (~ 3:00 AM CET)

Some jobs may have failed as a result.

We're working on resolving the problem and will update here with further information when we have it.

Thank you for your understanding.

Update 14:00 CET, October 22, 2017:  All systems have returned to normal operations and all jobs are now being processed normally.

tag:status.keboola.com,2013:Post/1199111 2017-10-19T14:39:27Z 2017-10-19T14:39:27Z Deprecating Redshift Bucket Credentials

In November 2014, we were really happy to announce a new cool feature -- Read-only bucket credentials to your Redshift backend. Time has passed and we have decided to deprecate this feature.

Though accessing data in a bucket is very useful, with the current scenario it can lead to an assumption how data is stored and how it'll be stored in future. The latter is much worse, because any change in our backend can lead to breakage of the system, which was programmed to access the data in a bucket.

Thus, we recommend you to access your data in a more robust way:

  1. Create a new Redshift Writer
  2. Choose a database provided by Keboola or your own Redshift database
  3. Configure which tables you need to synchronize
  4. Run the newly configured writer
  5. Copy the credentials created in step 2 to the software which needs to access your data

The existing Bucket credentials continue to work until April 18, 2018. However, we strongly recommend to migrate to the Redshift Writer as soon as possible.

The creation of new credentials and credentials listing will be disabled in the Storage section with the publication of this post.

Also, the Bucket credentials have been marked as deprecated in our Storage API.

Vladimír Kriška
tag:status.keboola.com,2013:Post/1197138 2017-10-10T10:31:36Z 2017-10-10T18:21:41Z Week in Review -- October 9th, 2017
The longstanding issue with slow SHOW DATABASES query executions on Snowflake has finally been resolved. We will now gradually enforce snowflake query execution limits where applicable by contract. Before turning the limits back on, we will check the query history and notify you if you may be affected.
(Query times in milliseconds)

New Features

Minor Improvements

We continue with cleaning up the KBC UI. So far, we have fixed many little annoying issues:

  • List of configurations now shows when the configuration was created (with exact date on hover) 
  • Cleaned up Job list (removed unused stuff).
  • Backend in Transformations is now preselected to default project backend.
  • CSV importer now supports .TSV and .GZ files too.
  • "Test Credentials" button and result polished.
  • Removed 'sticky' buttons when editing configurations.


  • Fixed files input mapping not showing in certain configurations.
  • Fixed a couple of errors with the Save button when editing transformation queries.
  • Fixed bug in Redshift writer with mixed case table names.


  • The encryption API is simplified to a single endpoint. If you manually encrypt values for KBC, please follow the docs. We will be contacting you if you are using the deprecated API calls.

Ondřej Popelka
tag:status.keboola.com,2013:Post/1195929 2017-10-04T12:49:43Z 2017-10-04T18:59:51Z Job Failures [Not Resolved]

Today, October 4, 2017, we experienced several jobs failures between 12:07--14:40 PM CEST. One of our worker servers became unresponsive which led to the jobs failures. We have shut down the instance and launched a new one. Everything is working properly now and we will further investigate the root cause of the issue. 

We're still encountering rare job failures. We're monitoring the issue closely and trying to find the root cause.

We are sorry for any inconvenience.

Ondrej Hlavacek