I have a workflow which runs daily. It has about 10 connections, among these two appends. I have one specific connection which I want to run more frequently. Moving this one connection into a separate workflow seems absurd. @"Willian from Sheetgo"#100 your take on this one?

I feel your frustration with this limitation @"Support from Sheetgo"#p460. However, this change would require us a massive amount of time in development and would break numerous business rules that we currently have. So let's keep this thread open to listen from other users about how much this improvement would benefit them over the current scheduling that we have. 😉

@"Willian from Sheetgo"#p463 I have a similar request. Like @"Support from Sheetgo"#p460 I have two workflows with almost the same connections. One runs once a day, one every four hours. When I change a connection in one workflow, I wish it to reflect that in the other one as well because as I said, the two workflows contain almost the same set of connections. Linux has a feature called symbolic links. A connection could reside in one workflow mainly but be linked to another workflow. However, changing the connection in the latter would actually change it in its primary workflow source. You understand what I am trying to say?

@"Willian from Sheetgo"#100 maybe nested workflows could be one way to solve this?

@"Eugenia"#p588 Yes, enqueuing workflows can solve the problem, however, @"Support from Sheetgo"#p460 said that he doesn't agree with splitting the workflow into small chunks.

@"Willian from Sheetgo"#p596 @"Support from Sheetgo"#1 why not?

@"Eugenia"#p689 sorry I'm not following. why not in regards to what?

@"Support from Sheetgo"#p697 why don't you want to use nested workflows for the different schedules?

Different schedule for specific connections

Willian from Sheetgo

Eugenia Yes, enqueuing workflows can solve the problem, however, Support from Sheetgo said that he doesn’t agree with splitting the workflow into small chunks.

Eugenia

Willian from Sheetgo @Support from Sheetgo why not?

paulmason

This is my issue as well. I want two automatic syncing on different schedules. One every 15 minutes during a certain time period (e.g., 1pm to 2pm) and then a sync every hour. I don’t know the solution but this is my problem I’ve been trying to solve.

Support from Sheetgo

paulmason then currently you need to duplicate your workflow to have a schedule different from the original workflow.

Willian from Sheetgo

paulmason Would you like to support this idea and upvote it? Highest voted entries features our roadmap 😉

Support from Sheetgo

Eugenia sorry I’m not following. why not in regards to what?

Eugenia

Support from Sheetgo why don’t you want to use nested workflows for the different schedules?

Support from Sheetgo

Eugenia I still don’t fully understand how nested workflows would help me.

Back to my example workflow with 10 connections, among them a couple of appends and one connection that I want to run more frequently than daily.

I want this connection to update every 4 hours but also as part of the main workflow to ensure data consistency.

How would I go about not duplicating this one connection to have it in two separate nested workflows?

Eugenia

Imagine you can group connections inside your workflow, you’d create a nested workflow with all the ones that you’d like to run in an increased frequency.
That way you can set two schedules: the one for the nested workflow and for the parent workflow.
With the advantage that: when running the parent workflow you run the nested one, but not the other way around
Does it make sense @Support from Sheetgo

Support from Sheetgo

Eugenia now it does, thanks!

Then I misunderstood the concept. Thought you wanted to nest an entire workflow inside another but the version you are outlining sounds like a perfect fit! :)

locomot1f

I’d support some type of nested workflow.

I too have this situation where I have a Workflow in which

One connection creates a tab in my worksheet, and then…
I have the next connection take that tab and split it to other Google Sheets.

It times out if I just let it run on a schedule. if i do one at a time, it obviously has no issues. I agree. separating that one connection out to another workflow is a bit absurd.

Karoline from Sheetgo

locomot1f Hi Ben, one workaround could be indeed you create a new workflow and then schedule the trigger on this 2n workflow to run based on the first. This could avoid the timeout (I’ll be checking this on my end)

locomot1f

☹️ says this option is only available for Business / Enterprise plans