How To Boost Flow Performance With earliestModifiedSince

Updates can pile up and degrade flow speed. earliestModifiedSince is an advanced feature you can quickly implement for better performance.

In this article:

• When to implement this feature
• How to implement earliestModifiedSince

When to implement this feature

When syncing large projects that involve multiple teams, it might take some time for a Unito flow to chew through all your updates.

earliestModifiedSince is a piece of code you can add to your flows that specifies a timestamp to limit the number of work items fetched by the initial sync and future resyncs. By implementing this, your flow will only sync work items that have been created or modified after a specific timestamp.

How to implement earliestModifiedSince

Start by going to the More Options tab of the flow editor. Scroll down to the Advanced Features text box. Copy this code:

{
  "earliestModifiedSince": 
}

And paste it into the text box. After this, you'll want to go to this Epoch Converter to get an exact timestamp marking the earliestModifiedSince date you want to use. Put in the date and time you want to use, and they'll be converted into a timestamp. Copy the number, making sure you get it in milliseconds — usually this will end in at least three zeroes.

Leave a space after the code's colon, then paste the Epoch in milliseconds. You should get something that looks like this:

{
  "earliestModifiedSince": 1489780800000
}

After you've put the code in, just save and close your sync. You should get better performance in no time!