Hi!
Are there any limitations on webhooks? It seems to me that grist sends only 10 rows in webhook payload.
I’ve tested this on self-hosted version and https://docs.getgrist.com, results are the same.
My test:
- Create table T1 with columns A, B, C and fill first 15 rows of column A.
- In the webhook panel create webhook: Event types: update; Table: T1; Columns: A.
- Select all rows (15) and paste (Ctrl+V) new data in column A.
Expected result: all updated rows (15) got into the webhook payload json.
Actual result: webhook sends first 9 rows and last one, the rest of the rows (5) are skipped. Webhook panel shows: “{“status”:“idle”,“numWaiting”:0,” … ,“lastEventBatch”:{“status”:“success”,“httpStatus”:200,“errorMessage”:null,“size”:10,“attempts”:1}"
1 Like
@Yan_Yablonskiy thanks for reporting this! This is unintentional, a bug that crept in. The webhook code uses some summarization logic whose defaults changed. We’ll work on getting it fixed. Sorry! We’ll look into it. Thought we saw a problem but I was premature.
1 Like
Hi @Yan_Yablonskiy.
It looks like this may be happening when columns to filter are specified. We’ll work on a fix, but in the meantime, if you are able to handle updates to all columns on the receiving end of webhooks, then it should no longer be limited to 10 rows. Let us know if that doesn’t work and thanks for reporting this.
George
2 Likes
Thanks for reply and amazing work on Grist!
Glad to be helpful. 
Hi @georgegevoian!
I’ll tweak my backend server. For now, webhooks without filter columns will work for me.
Thank you!
2 Likes