I have noticed when setting up coordinators which will materialize dozens of actions right away there is a delay of about 5 minutes before each action is created.
This is fine when the actions will take longer than 5 minutes on average but sometimes the action only takes a minute or two so the coordinator just sits there with no actions in the calendar for no apparent reason. The specific scenario I have now is reprocessing a few months worth of logs a day at a time and the coordinator has been submitted to process the past 60 days. Each action executes in about 150 seconds so another couple minutes are spent idle between each action. Would bumping up the concurrency help? If concurrency=2 would it materialize two actions per interval? thanks, Paul Chavez
