This must be a race condition situation. It’s writing the new row (second row) before the url has been written to the original row (first row).
Couple of things:
- First, it looks like you are still utilizing the same table to both obtain your recording as well as write a new row for that recording. They should be separate tables for simplicity. One table with ONLY ever one single row with the user specific column to obtain the recording from the recording component, and the other table with non user specific columns to permanently hold each recording and timestamp in separate rows. The way you are doing it with user specific columns for both the input and output in the same table is going to bite you some day. Only use user specific columns if you expect multiple users to update a column in the SAME row without interfering with other users.
- Second, I would add a ‘Wait For Condition’ action before the Add Row action. Set it to wait until the the recording column is not empty. This will allow for the recording to upload and process before writing the new row, so you should end up with the url as well as the timestamp in the new row