I’m wondering if some of these issues with Wrike “Updated” monitors could be related to a misunderstanding of the way Wrike monitors work.
For reference, here are some example “created” and “updated” times for what we see through the Wrike API for a given record:
Imagine you had a New Project and a Project Updated monitor both polling at the same time right after that updatedDate above. In our system (for Wrike only), this technically counts as a record that would get picked up by the “New Project” monitor rather than the “Project Updated” monitor. I definitely understand that this isn’t the most understandable behavior, but here’s the background on why we classify it that way for Wrike:
In Wrike, when you create a new record, most of the data entry happens right away. So, the createdDate and updatedDate will be identical (which makes it really easy to tell that it’s a brand new record rather than a record that got updated). However, certain fields in Wrike (the description is the main contributor to this issue) count in the API as “updates” rather than part of the creation process. So, we’d have Azuqua users using the “New Project” monitor, creating a new project in Wrike, giving that project a description, and then the “New Project” monitor wouldn’t pick it up because it would look like it had been updated rather than being a brand new record.
Our solution to this problem was to check if the createdDate and updatedDate are both within the same 5 minute polling period. This works in most cases, but if you update the record within those five minutes, the system actually considers it a “new” project rather than an “updated” project.
This may or may not explain some of the issues you’re experiencing with the Folder Updated trigger. Either way, I wanted to post it here so people can be made aware of it since it behaves differently than other Azuqua monitors.