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
Throttleduntil the load drops. Learn more about limits →
What you'll need
A database app
Unitswith a text fieldPrice list.A view of
UnitsnamedNot on 2027 price listthat only shows records wherePrice listIs not2027. To create it, open the app, selectFilter→Add filter, thenSave→Create new view. View filters aren't the same as automation filters, butGet viewuses the filters saved in the view.You need to be a workspace admin of the app's workspace and have
Full accessto the database app of the view. You can choose the app's team views and your own private views.
Build the batch automation
Open the
Unitsapp on desktop or web and click the automations icon in the top bar (tooltipCreate and view automations). The icon is only there for workspace admins.Select
New automation, then selectOn a scheduled time or interval.In the trigger, select
One timeand chooseEvery minute→15 minutes. The trigger now readsEvery 15 minutes, followed by the start date and time.Select
Add action→Get view. The step readsGet records of a view. Select the appUnits, then select the viewNot on 2027 price list.Click
•••on the action and turn onLimit results. The step then readsand limit results to. Enter 200 there.Select
Add action→Update collected. The step readsUpdate all collected records. Tape preselects the records fromGet view, listed under the app nameUnits.Select
Add field, selectPrice list, and enter 2027 inValue.Click
•••onUpdate collectedand turn onSilent, so 200 updates don't send notifications.Trigger automationsis off when you add the action, so the updates don't start other automations.Select
Create automation.
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 actionsafterGet view, select the records fromGet viewafterfor 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 lowerLimit resultsto match. Learn more about loop actions →Use a search instead of a view. Replace
Get viewwithSearch for recordsand add conditions withAdd filter.Pick another rhythm.
Every minuteoffers15 minutes,30 minutes,45 minutes, or60 minutes. For a nightly batch, chooseEvery day→1 dayand a time afteratinstead.Test first. Set
Limit resultsto 5 and check the five records before you raise it.
Learn more
FAQs
Why can't I update all records in one run?
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?
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?
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?
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 →.
