The time has come and the Restbox component as we know it is now being deprecated. But do not worry, its functionality will not disappear.

The Restbox component was once a great tool to collect data from various sources that were not complex enough to deserve a dedicated extractor (or writer) and shared similar processing aspects, such as decompression, audit tools, and CSV formatting. This has now been broken up into multiple separate components and processors to achieve or exceed the required functionality.

Today we have the following components to replace the Restbox component:

• S3 extractor
• S3 writer
• HTTP extractor
• Keboola Connection Storage extractor
• Keboola Connection Storage writer

Detailed documentation for most of them can be found at help.keboola.com.

The Restbox component is now available in the US region only, and, as of this announcement, no new configurations can be created. The component will be supported until November 1, 2018 when it will be finally shut down. Please migrate your configurations to one of the above-mentioned components. 

If you have any trouble migrating your configurations, please do not hesitate to contact us using the support button in your project.

Updated Components

• Dark Sky extractor supports future dates (and gets a forecast for up to 7 days ahead).

Minor Improvements

• Setting up MFA in Keboola Connection can display the code in plain text where QR is not available.
• We have changed Docker storage driver for Docker Runner job workers. We hope this will stabilize docker response times and minimize startup and shutdown overhead. This will be most significant when running short jobs.
• Editing components in Keboola Developer Portal got a facelift.

Unfortunately tonight there were a few more unexpected Application errors and delayed or longer running jobs between 1:25am–4:55am CEST (4:25pm–7:55pm) in the US region.

We have experimented with different storage drives (swapping from SSD to throughput optimized HDD) which lead to initial issues with building Custom Science apps. Attempts to provision further resources lead to too many running jobs at once (you could see "SQLSTATE[HY000] [1040] Too many connections" in the failed app events) and removing some of the additional resources could have yielded some other Application errors too. 

Currently we're running SSD drives again with enough resources to process all workloads. Please restart your failed jobs.

We hope we'll be able to stabilize this whole unfortunate situation as soon as possible and we're very sorry for inconvenience.

Unfortunately we we're unable to find a fix for yesterday's failures, so on Thursday June 7th between 3:49am CEST and 7:38am CEST (1:49am–5:38am UTC, 6:49pm–10:38pm PT) there was an increased application error rate on our Docker host instances in the US region.

The servers are now stabilized and it is safe to restart the failed jobs.

We're looking into this issue. We have started additional instances to help with the load and we'll be looking into the HW architecture of the instances to help us figure out what causes the issue. Meanwhile we'll try to implement a retry on such failed jobs.

We're sorry for this inconvenience.

On June 6th between 2:15am CEST and 2:35am CEST (5:15pm PT and 5:35pm PT, 12:15am UTC and 12:35am UTC) there was an increased rate of application errors on one of our Docker host instances in the US region. The instance is now fully operational and the jobs are safe to restart.

Furthermore one of our EU region Docker host instances went down at 6:56am CEST and caused a few unexpected application errors. There is a new one in place, we recommend restarting any failed jobs.

We're sorry for this inconvenience, we're working on preventing these errors in the future.

Between April 28 2:30 and 3:15 UTC there was a high rate of application errors on one of our instances processing component jobs. 

The instance was under heavy load and we're investigating the root cause. Instance is now back to normal and is safe to restart the jobs.

We're sorry for any inconvenience. 

Since Friday April 8, 2018, the SQLdep functionality in Transformations was returning an error. This was fixed today.

We're sorry for this inconvenience.

3:45pm CEST: We're investigating the issue.

3:55pm CEST: Not only starting, existing sandboxes do not seem to respond.

4:10pm CEST: We're shutting down existing sandbox instances and spinning up new ones. This will take a couple of minutes before the sandboxes will be available again. All existing sandboxes will be unfortunately deleted.

4:20pm CEST: Sandboxes are starting again. All previous sandboxes are deleted. We're sorry for this inconvenience.

New Components

• HTTP Extractor by Keboola. Read the release notes
• New version of Google AdWords Extractor supporting the latest API by Keboola. Read the release notes
• Fakturoid Writer by Keboola
• Collabim Extractor by Martin Matejka

New Features

• We have released the Guide Mode, an interactive tutorial for Keboola Connection
• "Sudo" mode - important changes are protected by requiring password

Updated Components

• Google Drive Extractor, Google Drive Writer and Google Sheets Writer all support Team Drives
• Google Sheets Writer preserves formatting when writing into an existing sheet
• Generic Extractor supports arrays as properties in child jobs.

Minor Improvements

• Encrypted values are now filtered from component events. This prevents accidental leak of credentials from a component, e.g. when it crashes as prints its stack trace or other internal logs to events
• keboola.processor-orthogonal is now available to fix malformed CSVs. Handy if you encounter Load error: Line 1 - Extra column(s) found errors

Another one joins the band.

In our effort to replace Restbox with modern components, the next logical step was the HTTP(s) extractor. It allows you to download a single CSV file or a compressed, publicly available file and import them into a single table in Storage. In case you have more public files to download from a single domain, the UI allows you to reuse the same base URL for more files.

The UI of the new extractor supports many features out of the box, but the extractor is not limited by its UI: it's another component that supports processors. So your CSV file can be invalid, in a weird charset, pivoted or mutilated in some other way, and there's tooling to get that fixed.

The list of available processors will be kept and updated in the Developer Portal list of components. A full description of the extractor is available in our documentation.