diff --git a/docs/assets/gettingstarted/airtable_skip_cron.png b/docs/assets/gettingstarted/airtable_skip_cron.png new file mode 100644 index 000000000..96ee69ff1 Binary files /dev/null and b/docs/assets/gettingstarted/airtable_skip_cron.png differ diff --git a/docs/your-first.md b/docs/your-first.md index 976980a21..d33523d3a 100644 --- a/docs/your-first.md +++ b/docs/your-first.md @@ -374,4 +374,19 @@ Try it out: - The new request will be in the Datastore, and if you open your reports endpoint tomorrow, you'll see a log of all the new requests, as well as updates to your Airtable base. +## One Last Thing + +At this point you'll have a cron that runs daily adding a row to your Airtable +project. Since we don't want that to happen forever you can do one of two +things. + +1. Click the pause button in the upper-left corner of the cron. +2. Add logic to your cron that will skip days that have no entries. + +If you want to do the latter, make the adjustment to the cron process by adding +the last 6 lines: assigning the length of todayRequests and then conditionally +emitting todayRequests to the StoreReport worker or not. + + ![assets/gettingstarted/airtable_skip_cron.png](assets/gettingstarted/airtable_skip_cron.png) + Congratulations! You now have your first Dark application: an API that stores requests into a datastore, creates a daily report of those requests, and sends the report to Airtable.