Thanks for the update. That complicates things a bit, but I’ve actually already solved for a situation like this. A while ago I created an automation that allows for more robust activity timing than Airtable’s “Record Timer” app. In short, it’s driven by a single-select field. Set it to “Start” and an automation saves a timestamp in the background (in a field that can remain hidden). Clear the single-select field and another timestamp is stored, and the difference between the two is calculated and output to a duration field. This can be repeated as many times as necessary, and the differences between the various timestamp pairs are all added up to give you a total of how long the record was in “Start” mode. This setup could be modified for your use case fairly easily. If this sounds like it’ll work, contact me directly and we can talk about the details.
