How often is the "Pre-built steps" search index built?

Integrator.io
1

Last night I needed a lookup for another flow in our Production account so I cloned it to Sandbox with a unique name so I could find it later. Feeling confident in the time savings I was about to realize, I changed to Sandbox, edited my flow and proceeded to attempt to add my newly cloned lookup.
No dice - it would NOT appear in the available pre-built steps on the right pane. I figured it must be a search index lag issue and decided to call it a night and try today. Hey, it's there now! So that's good, but also bad that we can't clone and use a step immediately.

A few questions:

  1. Is there an alternate method to add an existing step from another flow into the flow your working on? I imagine the IIO API can do this, but I've not yet tried and this client isn't allowing API access anyway due to lack of user-specific audit logging and granular scope/permissions.
  2. How often is the search index re-built? If I'm stuck with this current workflow it would be good to know how long I need to wait before trying to locate the item.
  3. Would be great if we could add Resources to flows from the Resources section. Find your lookup step, click menu icon and choose "Add to flow" with Environment, Integration and Flow selectors.
2
  1. If you have the id of the new step you made, then via api or the Zangabee chrome extension would be possible immediately.
  2. On average, it shouldn't be more than 30s, but I do see some rare cases where it's taking 1-5min. Will see if we can do anything here.
  3. The only downside of this is where does it go on the flow? It's more simple if the flow is small, but if it's a very complex flow I'm not sure the best place to put it (i.e. what branch, beginning, end, etc).
3

Tyler - You're back already!?

  1. Copy
  2. When I made my post I had waited hours without it showing up. After seeing your reply I just did a fresh test and the cloned export was available in a couple minutes. So I guess this was just a fluke.
  3. That's a good point - now that searching for existing steps is working like I would expect, this whole concept described in #3 isn't really valid.

I did just run into another unfortunate situation. I have a client that is subject to SOX controls. I wanted to clone a step from a production flow to sandbox. I recalled a dialog being presented when you clone that would prompt for destination environment, etc. Well, I cloned the step from the flow and it cloned it right away into the same flow. Turns out the behavior I remember is when you clone from the resources section.

Now I have an unauthorized audit log I need to write up and explain to the client. I can't really think when you would want to clone and immediately add the cloned object after the object you just cloned. This is a poor workflow. It should pop up the same dialog that is displayed when cloning from the Resources section.

4

A month flies by :slight_smile:

I and other users use the clone step all the time, it's our most used clone function. I often use it when I have branches and I need similar steps from other branches on new branches. So after clone, I just drag it to where it needs to be. We'll think about the feedback and see if there are additional options we can give without also making it more cumbersome than it is now.