No tasks showing up in query - super n00B

[saturdayxiii]

I just installed for the first time. My vault has a bunch of tasks scattered around, I wouldn't be surprised if the formatting is broken for some, but there are bog standard "- [ ] text" tasks that I'd expect to show up in a query.

I made a new note that copy pasted the global query example. It seems to work because the due date examples update with the correct date and there's that dynamic tally at the bottom that currently says "0 tasks".

I can't figure out how to make any of my tasks show up in the query. I've used the task creation modal to ensure correct formatting. I've tried setting the task tag in the global filter, and then removed it because who wants that.

I'm not sure what else would be causing a problem, but I assume I'm just doing something wrong or missing something basic.

I'm using Obsidian v1.4.16 on Win10 installed via scoop.sh with community plugins "Advance Tables", "Clear Unused Images", and "Homepage" installed along side Tasks.

Thanks for any help!

Edit for anyone with the same problem: I was treating the query block as multiple queries, expecting it to generate multiple lists of tasks, but the whole query block counts as a single query. Trouble shoot by starting with a single simple query:

```tasks
not done
```.

and see if any regular checkbox item comes up.

[claremacrae]

Thanks for using Tasks.

I've like to be able to help, if you can give some concrete information to work with.

Please read the following: https://publish.obsidian.md/tasks/Support+and+Help/Report+a+Bug

If you can provide full text, of a few tasks, and the query you are using, as per the above, I will willingly have a look when I have time.

Also, please let me what your global filter is, if any.

Thanks in advance.

[saturdayxiii]

Thank you for your help. I have removed the global filter option and restarted the program since I'd prefer not to use it, but it didn't have an effect.
Here is a note I'm trying, -00-TasksMisk.md:

- [ ] #task fix #saturdayxiii-blog tag generator
- [ ] #KASHA prints - Creation logo
- [ ] #KASHA Prints - design more
- [ ] Get #DirtyTraffik's stream to pop up on [website](https://dirtytraffik.live) when live

- [ ] test task
 - [ ] test task 2

#Tasks/Misc

and my query note is -00-AllTasks.md:

```tasks
# Only tasks that are not done, that is, which begin like this (but without the quotes):
#   '- [ ] ' or
#   '* [ ] ' or
#   '1. [ ] '
# Indented tasks are supported, but only single-line tasks.
not done

# Tasks due today or earlier:
due before tomorrow

due before next week

due before next month

due before next year

# Restrict to at most 100 tasks.
# If you ask Tasks to display many hundreds or thousands of tasks,
# Obsidian's editing performance really slows down.
limit 100

# Group and sort the output:
group by filename
sort by due reverse
sort by description

# Optionally, ask Tasks to explain how it interpreted this query:
explain

Which shows 0 tasks:

[claremacrae]

The query is matching only tasks that have a due date before tomorrow (as that is the earliest date).

None of your tasks have a due date, so they will never match that query.

It's probably best to start with a query that rules nothing out - and then gradually start adding filters.

Please see Due dates docs - and of course, do let me know if anything is still unclear.

[saturdayxiii]

I've tested due dates before and they didn't show up, but I must have been doing something wrong because you are right! I removed the due date query examples and now all my "undone" tasks are showing up.

Thank you so much for your help!

I was thinking that the query block worked as a list of multiple queries that the tasks would appear under each line, but now I understand that the whole block is a single query. I wouldn't have been so confused if the readme's "Create your first tasks search" didn't start with such a compounded example, but I'm very happy to understand it now, and those tiny unzoomable screenshots in the readme now make a lot more sense.

Thanks again for taking the time to point out my issue.