How fast Unito implements changes across your workflow depends on your plan, synced tools, and more.
What this article covers:
How long does Unito take to sync?
To keep your blocks of work up to date, Unito constantly monitors your blocks of work for any changes. How quickly those changes get carried over between blocks of work depends on a few factors:
- Your plan’s update time
- The number of changes to sync
- API response times
Some Unito plans, built for large teams, sync changes in real time. This means you can see updates happen in one tool minutes after something happens in the other tool. Other plans can sync changes within 5-15 minutes.
Some integrations don’t support webhooks, which are essential for syncing updates in real time. For these integrations, updates will take about five minutes to sync.
Even if you have a Unito plan with the fastest update time, it can take a bit longer for all your changes to sync over if you’re working with a huge amount of data. That’s because every new work item and every update isn’t a single action, but a sequence of actions that a Unito integration has to translate from one tool to the other. Extrapolate this over all your data, and that’s a ton of actions to sync over.
Let’s say you create a Jira issue and Unito needs to create a matching Trello card. Here’s an idea of all the actions Unito has to work through in just the first few seconds after that issue is created.
First, your Unito flow has to actually spot the Jira issue when it’s created. Then, it has to compare the specifics of that issue to any rules you’ve set in place. Does it have the right label? How about the assignee, is that right too? Only when your flow has checked through all potential rules settings can it decide whether to sync the issue or not.
Then it has to hop over to the Trello side, create the card, make sure it’s in the right list, and check that all fields match with what’s happening in Jira. That’s a lot of actions to go through in just a few seconds — and they all involve a ton of sub-actions as your flow interacts with each tool’s API.
This is just a short glimpse into some of the actions that go into keeping your work items synced in both directions. That’s why it can sometimes take a bit longer for larger data sets to sync over.
The actual time it takes to apply changes once they’ve been detected depends on the volume of changes and the response time of the tool APIs (e.g. how fast Trello can apply updates).
The advantage of live updates
You can speed up your workflows even further with the ability to collaborate across projects and tools in real-time! Instead of syncing every 5 to 15 minutes, changes made in your tools will be logged instantly and processed by your Unito flow.
Note that the speed at which this change is reflected in your other tool will vary on the size of your projects and the number of changes your flows need to process at once.
Wrike limitations
Due to constraints in Wrike’s API, the following limitations apply:
-
Changes to custom fields on a task in Wrike will not sync live; instead, they will take the usual 5 to 10 minutes to be detected.
-
Changes to tasks in sub-folders of your synced Wrike project or folder will not sync live; instead they will take the usual 5 to 10 minutes to be detected.