We have a Zapier > Slack task and it’s recently stopped finding the most recent firebase records. It seems Zapier is pulling through records based on key order (alphabetical) rather than chronologically. I’ve found documentation on “calling
setWithPriority and using
Firebase.ServerValue.TIMESTAMP to order by timestamp.” (https://zapier.com/help/doc/common-problems-firebase)...but I’m not sure how to do this in Zapier?
The Firebase Realtime Database has `users` with pushed objects (around 3000 objects/users at the moment):
This is the current set up of Zapier (although I’ve tried all sorts of options)…
When I run the test trigger all I get is…
None of the the most recent records come through. Based on the keys I’m seeing from the records it looks like Zapier is only pulling in alphabetically rather than chronologically. As you’ll see above, each record inside `users` has a `lastActive` property which is a standard epoc timestamp. I’ve tried to add `lastActive` to the Zapier `order` field but that doesn’t seem to work. Any ideas what we’re doing wrong?
Best answer by Paolo
I'm wondering if having lastActive and limit to last selected at the same time is causing a problem.
Would you mind:
- Clearing the location of the newest objects field
- Adding a new object that you would expect to see in this Zap
- Loading a new sample to see if that works
If that doesn't work, please let me know and I'd be glad to take another look at what's happening.