Since October 15, 2019 5:16PM UTC the Docker Hub container registry is experiencing a complete service disruption. Some of Keboola Connection 3rd party components' images are historically hosted on Docker Hub. Such components' jobs will fail during the outage. You can subscribe to the outage mitigation progress on Docker Hub status page.
All the new components and Keboola-maintained components are using AWS ECR as a registry, so they are not affected by the outage.
We're very sorry about any problems this may cause.
Since October 11, 2:00 PM UTC we are experiencing failures on the Transformation Overview page and on the Storage Table Graph page in all regions with the following error message:
Cannot load GoodData Writer: Client error response [status code] 410 [reason phrase] Gone
We're investigating the issue and will update this post with our findings.
We apologize for the inconvenience.
UPDATE October 15, 5:15 PM UTC: a new version was released and the bug was fixed.
New Components
- Smartsupp extractor by Revolt BI downloads data from the live chat platform.
Updates
- Input mapping filter can be set on an ignored column.
- Sandboxes with duration longer than 5 days display the expiration date correctly.
Updated Components
- Oracle and PostgreSQL extractors use optimized tables and columns loading.
-
R transformation and sandbox updated to version
3.6.1
.
R transformation supports R Markdown.
- GoodData Writer fixes the link to the GoodData project in the EU region.
Deprecations
- GoodData Writer V2, old OAuth Broker and the original AdForm extractor were successfully turned off.
Since October 10, 3:00 am UTC we are experiencing higher rate of "Obsolete output mapping" user errors in transformation jobs. This issue is caused by a recent update of the transformation component. We'll be rolling back the release as soon as possible and keep you updated on further events.
UPDATE 8:45 am UTC: We have successfully deployed a previous version and all affected configurations should be working now.
UPDATE October 13, 6:11 PM UTC: A new version with a fix has been released and deployed.
We apologize for the inconvenience.
There will be a maintenance period of Developer Portal on Saturday, October 12, 2019 from 6:00am UTC and should take around 1 hour.
We will be upgrading database infrastructure. This maintenance won't affect Connection nor any other Keboola service.
Date: Tue, Oct 8, 2019
Time: 6:00 PM - 7:00 PM CET
Learn about new features, functionalities, and components that we have built over the first half of the year.
Additionally, see the exciting plans that we have for the product for the next 3-12 months.
We hope that you can join us, but if not the webinar will be available on video by request afterward as well.
Cheers,
Your Keboola Team
The deprecated OAuth Broker won't be supported after September 30, 2019.
When executing configurations in not-yet-migrated projects, you will start getting errors with the end of life message. The migration will be available for at least one week after the deprecated Broker is shut down.
Please migrate your projects if you haven't done so already. If you have any questions, contact Keboola Support.
The support for the deprecated GoodData Writer v2 ends today, September 30, 2019.
The deprecated writer will start returning errors with the end of life message. You will be able to migrate for at least one week after the deprecated GoodData Writer is shut down.
If you are still using the deprecated GoodData Writer, you should see a deprecation notice in Keboola Connection. Please proceed to the migration.
If you need any help migrating the writer, contact Keboola Support.
On Saturday night, September 28-29th between 11:00pm - 8:20am we experienced failures of sending automated emails in EU region. Our monitoring shows only few jobs were affected, we recommend to double-check status of your recent orchestrations run. We apologize for the inconvenience.
A new release of the GoodData writer published on September 24, 2019, 3:17 pm UTC contained a bug affecting certain jobs in all regions. The bug caused the jobs to finish with an internal error.
We rolled it back to a previous version on September 25, 5:57 am UTC and all jobs are working now. We apologize for the inconvenience.