digdag sometimes uses local ./digdag.yml scope and sometimes global scope

[danielnorberg]

digdag schedules
2016-04-11 15:04:37 -0700: Digdag v0.5.9
Schedules:
  id: 2
  repository: dano-churn-prediction-poc
  workflow: +main
  next session time: 2016-04-13 00:00:00 +0900
  next runs at: 2016-04-12 15:00:00 -0700 (23h 55m 21s later)

1 entries.
Use `digdag workflows +NAME` to show workflow details.

and

digdag check
2016-04-11 15:04:54 -0700: Digdag v0.5.9
  System default timezone: America/Los_Angeles

  Definitions (1 workflows):
    +main (1 tasks)

  Parameters:
    timezone: "America/Los_Angeles"

  Schedules (0 entries):

As a user I'm really confused about how scheduling works =)

[frsyuki]

I don't understand what this ticket means. What YAML file did you push to server and what happens?

[danielnorberg]

I think I was confused about what digdag check does. I thought it was a client-mode command that queries the server about when workflows in a digdag.yml are scheduled to run, but it's just a local-mode command that shows how local digdag interprets the digdag.yml?

[frsyuki]

That's right, digdag check is a local-mode command. It's intended to be used when you want to validate your workflow before uploading it to server. To check schedules on the server, digdag schedules. Those commands need better organization but I don't have clear idea how to make it easy to understand.