Skip to main content

Update many records in batches

Change thousands of records without hitting run limits. A schedule works through a view a few records at a time, and each updated record drops out of it.

Written by Leo

One run can't update an unlimited number of records. A run stops after three minutes, can use up to 1,000 actions, and a single collection returns at most 1,000 records. For a large change, such as moving 2,400 rental units to a new price list, split the work. A view lists the records that still need the change, a schedule takes a batch from the view, and every updated record leaves the view.

Note:

  • Collections are cut off at 1,000 records. Tape doesn't show a warning when it truncates a collection, so keep the batch size well below that.

  • Too much activity delays everyone. Heavy use in a short time can throttle your organization. Runs that wait to start then show the status Throttled until the load drops. Learn more about limits →

The automation Move units to the 2027 price list with the trigger Every 15 minutes, Get records of a view in Units from Not on 2027 price list and limit results to 200, and Update all collected records with Price list set to 2027

What you'll need

  • A database app Units with a text field Price list.

  • A view of Units named Not on 2027 price list that only shows records where Price list Is not 2027. To create it, open the app, select Filter → Add filter, then Save → Create new view. View filters aren't the same as automation filters, but Get view uses the filters saved in the view.

  • You need to be a workspace admin of the app's workspace and have Full access to the database app of the view. You can choose the app's team views and your own private views.

Build the batch automation

  1. Open the Units app on desktop or web and click the automations icon in the top bar (tooltip Create and view automations). The icon is only there for workspace admins.

  2. Select New automation, then select On a scheduled time or interval.

  3. In the trigger, select One time and choose Every minute → 15 minutes. The trigger now reads Every 15 minutes, followed by the start date and time.

  4. Select Add action → Get view. The step reads Get records of a view. Select the app Units, then select the view Not on 2027 price list.

  5. Click ••• on the action and turn on Limit results. The step then reads and limit results to. Enter 200 there.

  6. Select Add action → Update collected. The step reads Update all collected records. Tape preselects the records from Get view, listed under the app name Units.

  7. Select Add field, select Price list, and enter 2027 in Value.

  8. Click ••• on Update collected and turn on Silent, so 200 updates don't send notifications. Trigger automations is off when you add the action, so the updates don't start other automations.

  9. Select Create automation.

In a new automation in Units, opening One time in the trigger, pointing to Every minute and choosing 15 minutes, so the trigger reads Every 15 minutes starting on 11/14/2026 at 8:00 AM

The result

Every 15 minutes, Tape takes up to 200 records from the view and sets their Price list to 2027. Updated records no longer match the view, so the next run picks up the next 200. With 200 records every 15 minutes, 2,400 units take about three hours.

When the view is empty, there is nothing left to do. The run still succeeds: Get view collects 0 records, so nothing is updated. Pause the automation or delete it.

Variations

  • Do several things per record. Add Loop actions after Get view, select the records from Get view after for each, and add the actions inside. Every step in the loop runs once per record, and steps that change records or send something count toward the 1,000 actions of a run, so lower Limit results to match. Learn more about loop actions →

  • Use a search instead of a view. Replace Get view with Search for records and add conditions with Add filter.

  • Pick another rhythm. Every minute offers 15 minutes, 30 minutes, 45 minutes, or 60 minutes. For a nightly batch, choose Every day → 1 day and a time after at instead.

  • Test first. Set Limit results to 5 and check the five records before you raise it.

Learn more

FAQs

Why can't I update all records in one run?

A run is limited to three minutes and 1,000 actions, and a collection holds at most 1,000 records. Batches keep each run inside those limits.

Why does the same record not get updated twice?

After the update, the record no longer matches the view's condition, so the view doesn't list it again. If a record keeps matching, the change doesn't touch the field the view checks.

How do I stop it?

Open the automation, select the status Active below its name so it switches to Paused, then select Save changes. Click ▷ next to Manual run to see what each run did.

Are you a developer using the Tape API for automations?

The automation API has its own documentation for developers. Full reference: collect_app_view_records in the developer docs →

Still have more questions? Find answers and get help from community experts in the Tape community →.

Did this answer your question?