After you schedule a cloud build, you follow it in three places: the Scheduled builds sheet, the status icon on the slate in the Day View, and the Mission Report that opens from that icon. The Mission Report follows the run from Queued to Complete, and its buttons open the result or download the CSV. A notification arrives when the run finishes.
Power plan. Cloud builds and the Scheduled builds sheet need an active Power subscription.
Before you start
- Schedule a build. See Schedule a cloud build.
The Scheduled builds sheet
Open it from the Playbook dropdown in the workspace (Scheduled builds) or from the pencil next to a playbook card's next-run line.
Each queued row shows the playbook (or "Scheduled build" for a run from the Build sheet), the lineup count, the fire time, and the lead before lock.
| Control | What it does |
|---|---|
| Change time | Opens Fire this build with 5 min, 10 min, 15 min, 20 min, and 30 min before lock. |
| Cancel | Cancels the run. |
A run scheduled from the Build sheet or the Automate builds sheet is not tied to a saved playbook, so the library's Scheduled filter does not list it. This sheet and the Day View do.
The status on the Day View
After you schedule, the slate's wrench turns into a status icon. Click it to open the Mission Report. After a cancel, the wrench returns.
The Mission Report
While the run is queued, the report shows the scheduled time and the Cancel schedule button. While it runs, the report shows the same stage headline, lineup counter, and contest rows as Mission Control for a browser run. See Run a playbook in the browser.
| Button | What it does |
|---|---|
| Cancel schedule | Cancels a queued build. |
| New build | After a finished or canceled run, opens the Build sheet for a new schedule on the same slate. |
| Open in Workspace | Opens the slate with the run's build tab selected. |
| Download CSV | Downloads the filled entries file. |
| Open DraftKings / Open FanDuel | Opens the site's upload page. |
Statuses
| Status | Meaning |
|---|---|
| Queued | The run waits for its start time. You can change the lead or cancel. |
| Running | The build is in progress. The lead can no longer change. |
| Complete | The pool is a build tab in the workspace, and filled entries are on the Entries view. |
| Failed | A step failed. The report shows the message, and the notification says which step. |
| Canceled | You canceled it. The slate on the Day View offers Build or schedule again. |
A run that stops on a guardrail with Stop the run completes without a fill; it is not a failure. The run notes show "Guardrail failed: ..." and the step summary reads "Run stopped by guardrail: <notice>".
Notifications
| Event | Title | Body |
|---|---|---|
| Run complete | "Your build is ready" | "<slate>: N entries ready to submit" or "<slate>: N-lineup portfolio ready" |
| Run failed | "Your build didn't finish" | "<slate>: stuck at <step>" |
| Run canceled | "Build cancelled" | "<slate>" |
A scheduled run sends an in-app and a push notification; an immediate run gets the in-app row only. No email is sent. See Notifications.
Open the result
- Click the notification, click Open in Workspace in the Mission Report, or open the slate from the Day View.
- The run's build tab is selected, with its per-contest sim results.
- Open the Entries view to check the filled entries, then export. See Cloud fill and export.
A workspace tab you kept open picks up the result on its own. A run from the Build sheet or the Automate builds sheet keeps its report for 7 days; filled entries stay.
Tips
- Open the Mission Report a few minutes after the ready time even without a notification.
- Cancel and reschedule instead of editing the Build sheet. The queued run holds a copy of the settings from the moment you scheduled.
- After a canceled or failed run, click New build in the report. It opens the sheet on the same slate.
Troubleshooting
"This build has already started. Cancel it instead." : a running build's lead cannot change. Cancel it and schedule again.
"This slate locks too soon to move the build. Cancel it instead." (lead editor) : no later lead fits before lock.
"This slate is locked, so the build can no longer run." : the slate started before the run fired. Use Late Swap on the entries you submitted.
"This build runs as soon as a slot opens, so it has no lead time." : an immediate run has no lead to change.
"Failed to update the schedule." or "Failed to cancel build." : the request did not reach DFS Hero. Try again.
"Your build didn't finish" with "stuck at <step>" : open the Mission Report, fix the cause it names, and schedule again.
"The build finished but its record could not be saved" (the message continues "the build tab would not appear. Re-run the build.") : schedule the build again.
A run shows Running long after lock : the run was interrupted. DFS Hero marks it failed after a few minutes and sends the failure notification.
Related
Was this article helpful?