Repository navigation
feat(automations): lists read each automation's triggers in words, with its runs today and next time - #580
Merged
Conversation
…th its runs today and next time GET /automations adds reads (match.describe_triggers: each trigger in words, then its join), runs_today and next_at (its soonest schedule, at, relative or join timer), for the studio's list. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AjJqXgjj1cNdKGRQbX5frb
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Adeel · project thread
Description
Before:
GET /api/v1/automationsgave each automation's triggers as JSON, with no way to say in a list what sets it off, how often it ran today or when it runs next.After: each automation in the list also has
reads, its triggers in words (“Email received”, where the subject contains “trip”; every weekday at 07:00 (Europe/London); a call to its webhook; then its join when there are several),runs_today(since midnight UTC, tries left out) andnext_at, its soonest waiting schedule, at, relative or join timer.match.describe_triggerandmatch.describe_triggersdo the reading, reusingschedule.describe, the kinds catalog's labels anddescribe_join.Motivation and Context
Workflow studio M11 (Studio UI), Build step 1: the list at
/automationsshows "a reading of triggers, ... last run, runs today, waiting, cost, next time". Agents get the same words over the API.Types of changes
!in the title)Checklist:
make hookschecks it on commit).test_automations.py::test_lists_read_the_triggers_in_words_and_say_when_it_runs_next,test_match_joins.py::test_triggers_read_in_words).docs/automations.md,docs/api.md.Local CI on this commit stacked on #576 (
--jobs backend,server,pre-commit): FastAPI embedded pass, FastAPI server pass, pre-commit pass.make openapioutput regenerated and unchanged on today's main.Done questions (AGENTS.md)
make openapitooling.schedule.describe, the kinds catalog anddescribe_join.Generated by Claude Code