Listing of users (GET /users), projects (GET /projects) and project users (GET /project-users) has been limited to 10000 results. To this moment listing of much more results didn't work anyway, Writer returned error instead of the listing. So if your writer contains more results and you have a script which process them, you will need to update it to support pagination. It works using parameters offset and limit (see docs for more information)
Amazon Simple Queue Service is reporting increased error rate in our main region. This affects majority of our applications and APIs. We hope for a quick fix, please bear with us, we'll post any updates here.
UPDATE 11:41pm PST / 08:41 CEST: We've migrated Storage API to SQS in a different region, so it's fully functional now. We're working on migrating all other APIs and apps to a different region as well.
UPDATE 00:05am PST / 09:05 CEST: All components should be working now, we're migrating process terminating queues (this bit is not working yet). You can restart your failed jobs.
UPDATE 00:52am PST / 09:52 CEST: Everything is back up and working normally. We're sorry for any inconvenience, you can now restart failed orchestrations and terminate all stuck or waiting processes.
MySQL Sandbox server is unreachable at the moment. Problem is caused by connectivity issues of our provider.
We are working on fix.
Problem is resolved. All sandboxes are accessible now.
On Wednesday at 9.15am PST We incorrectly configured sql_mode on the MySQL transformation server to value STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION.
This has caused many errors in you transformations and orchestrations - mostly with messages like
- Invalid datetime format: 1292 Truncated incorrect datetime value: ...
-
String data, right truncated: 1406 Data too long for column ...
-
Incorrect decimal value: '' for column ...
- Incorrect integer value: '' for column ...
We identified the error and fixed it on Thursday at 12.20am PST.
We are sorry for this inconvenience, we're working on setting up the environment so this error can't happen again. We tried to rerun all failed orchestrations, but if there's anything left, please restart the orchestration, everything should run correctly now.
New version v201506 of AdWords API has been released yesterday and our extractor will update in the beginning of August. Please be sure to update your configuration to not use unsupported metric names till the end of July. Also do not use new metrics until the update, we will let you know about it.
The API version (2.2) our Facebook Ads Extractor uses will be deprecated on 8.7.2015. We will therefore update the extractor to current 2.3 version. This change shouldn't affect the extraction according to the changelog: https://developers.facebook.com/docs/marketing-api/changelog
If your extractor fails, or delivers wrong data after 6.7., please let us know and we'll investigate what caused the problem.
In the past few days we encountered problems with imports from Google Drive.
These problems were caused by Google's auto-migration to "New Sheets".
If you have problem with your Google Drive Extractor, removing and re-adding the problematic sheet will fix the issue.
Be aware of your previous sheet configuration like "output mapping to SAPI table" or "transposition".
Contact support@keboola.com if you are not sure how to do it.
Oracle driver is now available in Database Writer.
Not all data types are supported yet, but this will change soon.
Facebook might have silently dropped permissions (read_insights and manage_pages) to the token provided in the Facebook Insights Extractor (ex-facebook). Your project might be missing insights data. Here are two simple steps to verify and fix this issue.
Verify your token's permissions
Paste the token(s) you have stored in the configuration into the debugger tool https://developers.facebook.com/tools/debug/ and look for the permissions in the results. If both read_insights and manage_pages are present in the Scopes section, your token is valid.
If not, please create a new the token.
Create a new token
Go to https://syrup.keboola.com/ex-facebook/token and authorize our extractor with access to your account. You'll get a new token that you can paste back to your configuration.
Backfill
If you have any gaps in your insights data, you can increase the overlap periods to automatically backfill the missing data or specify the period manually. See documentation for more details, if you're stuck, get in touch with us here in the comments section or at support@keboola.com.
Our Elasticsearch Syrup cluster is not responding. This cluster stores all information for all components' jobs. Storage works fine, but the rest of the system came to a halt. We're investigating this issue.
UPDATE 10:30pm PST / 7:30am CEST: Cluster is back online, all operations resumed or restarted. We're sorry for any inconvenience.