UI Scheduler Issues

[zanesq]

Describe the bug

Scheduler functionality isn't running at the exact time and its not able to load the session from a run. Also when trying to setup a schedule using cron and run it manually I got a unexpected response format error.

To Reproduce
Steps to reproduce the behavior:

1. Create a schedule from a recipe
2. Run schedule
3. See errors

Expected behavior
It should launch at the specified time and it should allow loading the session information.

Screenshots

Please provide following information:

• OS & Arch: [Mac Arm]
• Interface: [UI]
• Version: [v1.9.1]
• Extensions enabled: [Developer]
• Provider & Model: [Claude 4]

Additional context
Add any other context about the problem here.

[junweiz-block]

I have a scheduler set up and it supposes to run at 9:48 am daily, My local time zone is Australia/Melbourne, when the time arrives, the scheduler doesn't run.

When I manually trigger a run, the new run shows a created at timestamp that's in the future.

When I click that run, Goose is unable to load run detail

Please provide following information:

OS & Arch: [Mac Arm]
Interface: [UI]
Version: [v1.9.1]
Extensions enabled: [Developer, Context 7, Fetch, Memory, Playwright, Slack, Websearch, Linear]
Provider & Model: [Claude 4 Sonnet]

[Abhijay007]

Feels like it is related to this one: #4603 , as @iandouglas shared that it requires having a prompt field, maybe it is not getting that in those recipes and failing due to that.

[iandouglas]

Not having a prompt is one thing, running at a completely unrelated time of day is another and could be a separate issue? We'd need to see some logging or debugging to know when it's actually starting, what's going on with its internal process etc.. Any chance you can check the .jsonl for timestamps to see if it's starting on time or not and what the first couple of responses are from goose?

[junweiz-block]

Hi my goose schedule looks like

 {
    "id": "daily-breaking-news",
    "source": "/Users/xxx/.local/share/goose/scheduled_recipes/daily-breaking-news.yaml",
    "cron": "5 9 * * *",
    "last_run": "2025-10-07T09:15:04.676537Z",
    "currently_running": true,
    "paused": false,
    "current_session_id": null,
    "process_start_time": "2025-10-07T09:15:04.676537Z",
    "execution_mode": "foreground"
  }

And /Users/xxx/.local/share/goose/scheduled_recipes/daily-breaking-news.yaml looks like

title: Breaking News Aggregator Recipe
description: This recipe fetches breaking news from CNBC and Bloomberg websites,
  focusing on the last 24 hours of headline news, tech news, AI news, business
  and market news. It consolidates duplicate stories and provides a curated list
  of the top 10 breaking news items with titles, summaries, and URLs.
instructions: >-
  You are a news aggregation assistant that fetches and consolidates breaking
  news from major financial and technology news sources.


  Your task is to:


  1. **Calculate accurate timestamps**: Determine the exact time range for "last
  24 hours" using shell commands to get current time and calculate 24 hours ago
  in UTC format.


  2. **Fetch news from CNBC**:
     - Navigate to https://www.cnbc.com/world/?region=world (main page)
     - Navigate to https://www.cnbc.com/technology/ (tech section)
     - Extract recent news stories focusing on:
       - Headline/breaking news
       - Technology and AI news
       - Business and market news

  3. **Fetch news from Bloomberg**:
     - Navigate to https://www.bloomberg.com/asia (main page)
     - Navigate to https://www.bloomberg.com/technology (tech section)
     - Extract recent news stories focusing on:
       - Headline/breaking news
       - Technology and AI news
       - Business and market news
       - Cryptocurrency and financial markets

  4. **Filter by timeframe**: Only include news published within the last 24
  hours based on the calculated timestamps.


  5. **Consolidate and deduplicate**: Remove duplicate stories covering the same
  events from both sources.


  6. **Generate final output**: Create a markdown-formatted list in Chinese
  language of exactly 10 top breaking news items, each containing:
     - **Linked title** (max 20 words)
     - **Short summary** (1-2 sentences, max 20 words)
     - **Source URL** attached to the title

  ## Output Format

  The final output should be formatted as a markdown document with:

  - A main heading indicating the time range

  - Each item formatted as: `[**Title**](URL)` followed by summary

  - Footer note indicating sources and compilation timestamp


  ## Tools Required

  - `playwright__browser_navigate` - for accessing news websites

  - `playwright__browser_snapshot` - for capturing page content

  - `developer__shell` - for calculating timestamps

  - Standard text processing and analysis capabilities


  ## Example Output Structure

  ```markdown

  # Breaking News from the Last 24 Hours (Date Range)


  ## [**News Title Here**](https://example.com/article)

  Brief summary of the news story in 20 words or less describing the key
  developments.


  ## [**Another News Title**](https://example.com/article2)

  Another brief summary explaining the important aspects of this breaking news
  story.


  [Continue for items 3-10...]


  ---

  *Note: Compiled from CNBC and Bloomberg on [date], focusing on breaking news
  from the previous 24 hours.*


  ## Success Criteria

  - Exactly 10 news items

  - All items published within last 24 hours

  - No duplicate stories

  - Mix of headline, tech, AI, business, and market news

  - Proper markdown formatting with working URLs

  - Summaries under 20 words each

  - Clear source attribution
activities:
  - Generate
schedule:
  foreground: true
  fallback_to_background: true
  window_title: Breaking News Aggregator Recipe - Scheduled

In terms of the .jsonl file, goose didn't create sessions for the scheduled runs today which it should, the most recent session from a scheduled task looks like:

{"working_dir":"/Users/xxxx/xxxx","description":"Empty job - no prompt","schedule_id":"daily-xxx-slack-monitor","message_count":0,"total_tokens":null,"input_tokens":null,"output_tokens":null,"accumulated_total_tokens":null,"accumulated_input_tokens":null,"accumulated_output_tokens":null,"extension_data":{},"recipe":null}

[iandouglas]

Yeah you can see with the session file that it found no prompt. You have an instructions set but you'll need to add a prompt to the file, even if that prompt just says "follow the instructions for my task"

[DOsinga]

I believe the prompt is the only thing it cares about and it will ignore the instructions

[junweiz-block]

You have an instructions set but you'll need to add a prompt to the file, even if that prompt just says "follow the instructions for my task"

How to do that for scheduled tasks? I don't see there is a field related to "prompt" when creating or updating a schedule.

[iandouglas]

How to do that for scheduled tasks? I don't see there is a field related to "prompt" when creating or updating a schedule.

You add a prompt when you create the recipe. You can find the recipe file that goose made and add a prompt instruction manually. Check the following disk paths:

• ~/.local/share/goose/scheduled_recipes/
• ~/.config/goose/recipes/

[iandouglas]

related discussion: #4603

[junweiz-block]

After recreating a recipe with some initial prompt and create a new schedule task with that, now the schedule does kick off on manual run.

But the schedule doesn't work as expected:

1. Created timestamp is wrong, it shows some timestamp in the future.
2. Goose complains it doesn't have any tools to do the task, but they do exist and manually run the recipe works with those tools.
3. Cron Job didn't triggered automatically when the time arrives, which it supposed to.

[iandouglas]

Add an 'extensions' key in the recipe so it knows which extensions you want it to use.

[junweiz-block]

Add an 'extensions' key in the recipe so it knows which extensions you want it to use.

Yes, I can do that.
But I think we should at least update the recipe creation UI to include that field, or the even better and intuitive way is that Goose can automatically fill in extensions based on the chat conversation details when user clicks "Create a recipe from this session".

[iandouglas]

yeah, if you're asking goose to make the recipe for you, I agree it would be nice if it could look at which extensions it needed in the session to include them