DATAFLOW AUTOMATION RELEASE NOTES
RELEASE DATE: 7.6.2017
BUG FIXES
- Fixed an issue where null in a date field would not write to SQL Server.
- Fixed an issue where the error message returned from an action would be blank.
Enhancements
- Dataflow Webhook Rate Limiting is now enforced to ensure a high quality of service. The limits are shared between all webhooks within the Dataflow and reset every 60 seconds.
What is the limit?
|
Records Per Dataflow Webhooks |
Reset Interval |
|
100 Records |
60 seconds |
What happens when I exceed the limit?
If 100 records are exceeded within 60 seconds, the Webhooks will NOT receive any more information until the reset interval hits.
An HTTP 429 message will be sent back to the source that sent the request.
PLEASE NOTE: If using Zerion Data Collector or iFormBuilder, ensure Guaranteed Delivery is turned on to ensure the record will re-try and make it to dataflow.
Examples
- 100 records are sent within 50 seconds, it is shut down for next 10 seconds.
- 100 records are sent within 30 seconds, it is shut down for next 30 seconds.
- 100 records are sent within 40 seconds, it is shut down for next 20 seconds.
Scenarios
- If you include 101 records in a single request the entire message will be rejected and return a 429 response back.
- If you have 10 users all submitting 20 records within 60 seconds, some of the records will get rejected depending on the timing of when they are submitted. When the records fail they will return back a 429 request.
- If you have 3 webhooks setup on a single Dataflow, this limit is shared between all the Webhooks. You can send 40 records to a single webhook, 60 to another webhook and then for the next 60 seconds none of the webhooks can receive any records.
Comments
2 comments
Dataflow Automation 2.7 release is now available.
We have just deployed a patch to 2.7.
This addresses an issue where sometimes you could not save a SQL Server action. This is now fixed and is available in production.
Please sign in to leave a comment.