A cloud build runs a playbook on DFS Hero's side at a lead time you pick, 5 to 30 minutes before the slate locks. Your tab can be closed. The run builds the pool, simulates against your entered contests, selects the working set, and fills your uploaded entries. When it finishes, the pool appears as a build tab in the slate's workspace and a notification tells you the entries are ready to download.
Power plan. Cloud builds need an active Power subscription. The When row is not shown on Essential.
Before you start
- Upload the entries CSV to the slate. A slate without entries cannot be scheduled. See Upload your entries.
- Decide which settings should run: the slate's Build Settings, or a saved playbook. See What is a playbook.
- Check the lock time. A lead time that has already passed is disabled.
Path 1: the When row in the Build sheet
This path schedules the settings in the sheet, from the Day View or the workspace.
-
On the Day View, find a slate with entries and click the hammer (Build or schedule). In the workspace, click the build button at the right end of the toolbar. It reads Simulate when Build Mode is on Build & Sim.
-
Set up the build: Build Only or Build & Sim, lineup count, randomness, stacks, and the rest.
-
In the footer When row, click a lead time: 5m, 10m, 15m, 20m, or 30m. Now builds at once. A lead time that cannot finish before lock at this lineup count is greyed out. The info icon next to When explains the row.
-
Check the caption above the row. Make sure the ready time leaves you enough time to download and upload before lock. The caption also lists settings that do not travel under "Not applied".
-
Click Schedule (or Schedule & Simulate for Build & Sim).
-
The Mission Report opens with the status Queued, and the slate opens as a tab in the top bar. See Scheduled builds.
The sheet schedules a copy of the settings as they are at that moment; changing the sheet later does not change the queued run. Scheduling again on the same slate replaces the queued run.
Path 2: schedule a saved playbook on a slate
-
Open Playbooks, click Actions on a card, and choose Schedule for a slate….
-
Pick one of today's slates. A locked slate is disabled.
-
Under Run it, pick 5 min, 10 min, 15 min, 20 min, or 30 min before lock. A lead that already passed is disabled.
-
Click Schedule on <slate>.
The dialog lists today's slates only. This path ties the run to the saved playbook, so the card shows the next run and its pencil opens the schedule.
Path 3: Automate builds for every slate with entries
-
On the Day View, click Automate builds in the stats bar. The sheet lists every slate of the day with entries.
-
Use Run all to pick one lead time for every row (Now, or 5 min to 30 min), or set each row on its own.
-
In each row, pick the playbook. The default playbook is preselected. A row with no matching playbook offers a link to create one in the library.
-
Tick the checkbox of each slate to build. The footer button counts the ticked slates.
-
Click Schedule N builds (Build N now with Now selected).
Scheduled rows run in the cloud at the lead time, even with the app closed. Now rows run in this tab, one at a time; keep it open until they finish.
Path 4: Auto-schedule on upload
Auto-schedule is a setting of the default playbook. When it is on, every entries upload for a slate of that sport, site, and mode schedules a cloud build at the chosen lead.
-
Open Playbooks and click Actions on the default playbook (the one with the star). If no playbook is the default, choose Set as Default first.
-
Open Auto-schedule and pick 5 min before lock, 10 min before lock, 15 min before lock, 20 min before lock, or 30 min before lock. Off turns it off.
No run is scheduled when the slate is locked, when the upload lands inside the lead window, when the playbook's lineup count is over your build limit, when the playbook needs reconfiguration, or when a run already exists for that slate.
How it works
The lead time is a delivery promise, not a start time. DFS Hero estimates how long the build takes and starts early enough to finish by lock minus the lead. When no lead can be kept at the lineup count, the caption names the earliest lead it can promise; lower the count or pick that lead.
The run follows the playbook stages: build, one sim per entered contest (Build Only skips the sim), the After build guardrails, selection, the Before fill guardrails, and the entry fill. The whole pool is saved, and the finished run appears as a build tab in the slate's workspace on any device.
A cloud run never exports. Download the CSV from the Entries page or from the Mission Report's Download CSV button. See Cloud fill and export.
While a run is queued for a slate, the Playbook dropdown leaves that slate's toolbar. It returns when the run finishes or you cancel it.
Tips
- Pick 30m for a full Build & Sim on a big slate. It leaves you time to open the result, check the exposures, and export before lock.
- Pick 5m or 10m for a small Build Only cash playbook when you want the latest news priced in.
- Set a default playbook per sport and site and turn on Auto-schedule. Every entries upload then schedules itself.
- Use Automate builds on a Sunday with several NFL slates. One sheet, one click.
Troubleshooting
"Scheduling requires a Power subscription." : upgrade or resume the subscription in Settings.
"That lead time has already passed for this slate." : lock minus the lead is in the past. Pick a shorter lead or run Now.
"A build is already running for this slate." : wait for it, or cancel it from the Mission Report.
"This playbook does not match the slate" or "Settings sport/site do not match the slate" : pick a playbook for the slate's sport, site, and mode.
"This playbook needs reconfiguration before it can run." : open the playbook, set the stages, and save.
"The playbook changed while scheduling it. Try it again." : the playbook was edited during the request. Click Schedule again.
"Failed to schedule build." : the request did not reach DFS Hero. Check the connection and try again.
"Can't be ready by then at this lineup count" (chip tooltip) : lower the lineup count or pick a shorter lead.
"Upload entries first to build" (hammer tooltip) : the slate has no entries file. Upload one, then schedule.
"Slate is locked" (hammer tooltip) : the slate started. Use Late Swap on your filled entries.
Related
Was this article helpful?