Default playbooks and cloud builds in parts

Last updated Nov 19, 2026

When your defaults for a sport and site include a playbook built for some contest groups, DFS Hero can run all of them on a slate at once. Each default playbook takes the entered groups it covers, and the fallback default takes all other contests. The run is one build in parts: one part for each playbook, done one after another. Each part builds, simulates, selects, and fills its own contests, and lands as its own build tab.

Power plan. Playbooks, cloud builds, and the Automate builds sheet need an active Power subscription.

Before you start

Which playbook covers which contests

DFS Hero gives each entered group to the default whose Built for list holds it. Every other group goes to the fallback default, as All other contests. With no fallback, a group that no default holds gets no part, and its contests keep the lineups they hold.

A run now gives no part to a default with none of its groups on the slate. A scheduled cloud build keeps a part for every default, because your entries file can change before it starts, and skips a part that holds no entered contest at its start.

For example, with a default for Cash, a default for Single entry, 150-max, and a fallback, a slate with cash, 20-max, and 150-max contests runs three parts:

PartPlaybookContests
CashThe Cash defaultThe cash games
150-maxThe Single entry and 150-max defaultThe 150-max tournaments
All other contestsThe fallbackThe 20-max tournaments

Run the defaults now from the slate menu

  1. On the Day View, open the slate's three-dot menu and point at Run Playbook.
  2. Read the first row, Default playbooks. Its second line says what it runs, for example 3 playbooks · Cash, Single entry, 150-max, all other contests. A third line names an entered group that no default covers, for example No default playbook covers 20-max. Point at the row to read each part with its playbook.

  1. Click Default playbooks. The parts run in this browser tab, one after another, each on a new build of its own groups. Keep the tab open until they finish.

The row shows only on a live slate where a default has groups. Under it, each playbook of the menu names the contests it covers, such as Cash or All contests. The playbook icon in this menu marks the fallback default only; the library and the workspace picker show a star on every default.

A part that fails never stops the parts after it. The message Some default playbooks did not run says what failed. Cancel in Mission Control stops the run: the parts after it do not start, and the message Default playbooks canceled names the part you stopped and each part that did not run.

The second line readsWhy the row is off
The slate is lockedThe slate started.
A build runs on this slate nowAnother run holds the slate. Wait for it.
Loading this slate's contestsThe groups of your contests are on their way.
This slate's contests did not loadThe groups of your contests did not arrive. Close the menu and point at Run Playbook again: the row asks for them again.
A default playbook needs setupOpen that playbook with Edit, set the stages, and save.
No default covers an entered contestNo default holds a group of this slate.

Run or schedule the defaults from Automate builds

  1. On the Day View, click Automate builds in the stats bar.
  2. A slate where a default has groups starts on Default playbooks. The lines under the row name each part, for example Cash: Cash Grinder and All other contests: Milly GPP, then any group no default covers.

  1. Pick Now, or a lead of 5 min to 30 min before lock.
  2. Tick the slate and click Schedule N builds, or Build N now with Now.

A Now row runs its parts in this tab, one after another. A scheduled row schedules one cloud build in parts, which runs with the app closed. See Schedule a cloud build.

After you schedule, the row names the parts the build stored, then any entered group that no part covers, for example No default playbook covers 20-max. The queued build names those groups too: on the last line of its status icon's tooltip on the Day View, and in its Mission Report, which says that those contests keep the lineups they hold.

The playbook list of each row names what each playbook covers, for example Cash Grinder · default for Cash, Milly GPP · default for all other contests, or SE Builder · Single entry for a playbook with a list that is not a default. A row on one playbook with a list names what it covers on the slate, for example Cash: Cash Grinder, or · No entered contest when the slate holds none of its groups, then No playbook covers and the entered groups it leaves out.

When a default needs reconfiguration, a Default playbooks row starts unticked, its lead times are off, and its line names the playbook to fix, for example "Cash Grinder" needs reconfiguration before it can run. In the row's playbook list, that playbook reads · needs setup.

Schedule one playbook built for some groups

Schedule for a slate… on a playbook with a Built for list schedules one cloud build of that playbook's groups only. The dialog says so, for example "It builds and fills only your Cash contests." The other contests keep the lineups they hold. A later edit of the playbook does not change a run that is already scheduled.

Auto-schedule with several defaults

Auto-schedule is a setting of each default playbook. When you upload an entries file, DFS Hero schedules one cloud build in parts for the slate:

  • Each default with Auto-schedule on gets a part for its groups.
  • A default with Auto-schedule off gets no part. Its groups do not go to the fallback either, so their contests keep the lineups they hold.
  • The run delivers by the earliest deadline of those defaults, so the longest lead decides.
  • When no part holds an entered contest of the new file, no run is scheduled.

How a cloud build in parts runs

  • One slate holds one cloud build at a time. The parts run in turn and all deliver by the run's deadline.
  • At its start, the run reads your entries file one time and gives each contest to one part. A later upload or change moves no contest.
  • A part with no entered contest is skipped and reads No entered contest. With no entries file at all, a part for chosen groups reads No entries file, and the part for all other contests builds with no fill.
  • When a part fails, the fills of the parts before it stay, and the parts after it still run.
  • When the slate locks before a part starts, that part and every part after it read Slate locked first.
  • An entered contest that no part covers keeps the lineups it holds.

The Scheduled builds sheet lists one line for each part, for example Cash: Cash Grinder · 150 lineups. Once the run starts, each line adds its status. See Scheduled builds.

Read the Mission Report by part

The Mission Report of a build in parts shows one section for each part, in run order. Each section names the part's groups and its playbook, its status, its lineups, its filled entries, and its contests, with one row per contest as in any run.

StatusMeaning
WaitingThe part did not start yet.
RunningThe part is building, simulating, or filling now.
CompleteThe part built and filled its contests.
StoppedA guardrail stopped the part.
FailedThe part hit an error. The section shows the message.
Slate locked firstThe slate locked before the part started.
CancelledYou canceled the run during this part.
No entered contestThe slate holds none of the part's groups.
No entries fileThe slate had no entries file at the run's start.

The last section, Not covered by any playbook, lists the entered contests that no part covered. The contests with an entry that still holds no lineup come first, under a Not filled tag: their count and up to five names, for example 2 entered contests · this build left them as they were. The contests whose entries all hold lineups, because another build filled them, follow with no tag, for example 3 entered contests · their entries already hold lineups.

When a part left its contests unfilled, or a contest that no part covered still has an entry with no lineup, the report opens with Build finished, some contests not filled, and its status reads Some not filled. A contest that another build filled is no problem: a scheduled build for one group, such as a build for Cash, reads Build Complete when your other builds filled every other contest. When every part was skipped, it opens with Nothing was built, and its status reads Nothing built.

Open in Workspace opens the slate. Each part that built is its own build tab, and a part for chosen groups shows their tag on its tab.

Notifications

EventTitle
Every part filled its contests, and every contest with no part holds lineups"Your build is ready"
A part did not fill, or a contest with no part has an entry with no lineup"Build finished, some contests not filled". The body names each part that did not fill and the contests with no part that are not filled.
Every part was skipped"Nothing was built". The body reads "<slate>: none of your entered contests are in this run's contest groups." and names each part.

See Notifications.

Tips

  • Keep one fallback default with no list for each sport and site. Without it, a group that no default holds gets no build.
  • Read the third line of Default playbooks before lock. No default playbook covers names the contests that stay as they are.
  • Download the CSV after the whole run, not after one part. Each part fills only its own contests.

Troubleshooting

"No default playbook covers 20-max" : no default holds that group, and you have no fallback. Set a fallback default, or a default built for that group.

"No entered contest" on a part : the slate holds none of that part's groups. Nothing to fix.

"Not covered by any playbook" with Not filled in the Mission Report : those contests had no part, and an entry in them still holds no lineup. Build them in the workspace, or add a default for their group. Contests in that section with no tag already hold lineups: nothing to fix.

"Default playbooks canceled" : you canceled the run. Open the slate to see the parts that ran.

Was this article helpful?