# CALL API skipping mutations **URL:** \ **Category:** Ask for Help\ **Created:** [May 29, 2024, 7:18am UTC](https://community.glideapps.com/t/call-api-skipping-mutations/73733 "2024-05-29T07:18:33Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![abdo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/abdo/32/36540_2.png) [@abdo](https://community.glideapps.com/u/abdo)\ **Post date:** [May 29, 2024, 7:18am UTC](https://community.glideapps.com/t/call-api-skipping-mutations/73733/1 "2024-05-29T07:18:33Z")
I am using call API to update a current timestamp in multiple rows at the same time. I just realized that CALL API is skipping mutations sometimes. Any idea why & how I can track this? This is using Glide builder. I will test from the app as well. ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [May 29, 2024, 7:44am UTC](https://community.glideapps.com/t/call-api-skipping-mutations/73733/2 "2024-05-29T07:44:05Z")
I would start by checking the action log run history to see what was actually sent. ---
**Author:** ![abdo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/abdo/32/36540_2.png) [@abdo](https://community.glideapps.com/u/abdo)\ **Post date:** [May 29, 2024, 8:02am UTC](https://community.glideapps.com/t/call-api-skipping-mutations/73733/3 "2024-05-29T08:02:01Z")
Thank you @Darren_Murphy great tip. Will check this immediately, the next time this happens. Do you know any reasons a mutation can be skipped (although the total count is only 3-4) When we roll this out, it will have 300-400 mutations per call API ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [May 29, 2024, 8:06am UTC](https://community.glideapps.com/t/call-api-skipping-mutations/73733/4 "2024-05-29T08:06:47Z")
How are the mutations prepared? I have seen unexplained failures when using the JSON Object/JSON Template columns in conjunction with Trigger Webhook, so I don’t have absolute confidence in them. I’ve also found that Call API can be very slow when sending large numbers of mutations to the Glide API, and so I tend to avoid it as well. For bulk mutations (which I do a lot of), I’ve found the most reliable (and fastest) approach is to prepare the mutations with normal Template columns, and send them via Make as a webhook. ---
**Author:** ![abdo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/abdo/32/36540_2.png) [@abdo](https://community.glideapps.com/u/abdo)\ **Post date:** [May 29, 2024, 9:07am UTC](https://community.glideapps.com/t/call-api-skipping-mutations/73733/5 "2024-05-29T09:07:42Z")
That is a bit worrying now for me… Mutations are prepared using JSON Object column and then lookup etc… There is a button that triggers the Call API and the body contains the mutations. We go to a partner and pick up 200 items… I want to set a timestamp for every row of the pickup action. Previously we stored a pickup global timestamp & then each item can have a computed pickup value etc… But now I want to set the pickup timestamp in the row as a basic column. I will be tesing this with a larger number of rows later this week… but would do you have more insight on the time expected for 300-400 mutations? and the cost of sending them to MAKE instead? I was hoping we don’ thave to go through MAKE since Glide has a Call API ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [May 29, 2024, 9:30am UTC](https://community.glideapps.com/t/call-api-skipping-mutations/73733/6 "2024-05-29T09:30:29Z")
The problem with the Call API action is that it blocks while waiting for a response from the Glide API, so if you’re sending a large number of mutations the delay while the Glide API processes them and responds can be quite significant. Which results in a crappy user experience. When you send a webhook, it’s basically “send and forget”, so from an end user perspective it’s a much better experience. In terms of Make operations cost, as long as you batch them and don’t send one by one, then the cost is negligible. ---
**Author:** ![abdo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/abdo/32/36540_2.png) [@abdo](https://community.glideapps.com/u/abdo)\ **Post date:** [May 29, 2024, 11:00am UTC](https://community.glideapps.com/t/call-api-skipping-mutations/73733/7 "2024-05-29T11:00:29Z")
Let me check what the delay is. Its better for us that the app waits for the response before proceeding. Lets hope its not minutes!!