Skip to content

[FEATURE] scheduled triggers: display schedule (including next run time) in CLI-echoed info #226

Open

Description

@brahn

Description of the problem being solved

As a slack app developer, when I update a scheduled trigger's frequency or other scheduling details, I want to be able to verify that my update worked as I expected immediately, rather than waiting to see if it runs when I expect.

It would be extremely helpful to be able to see the schedule details, especially the next expected run time, when viewing the trigger's other details (e.g. by running slack trigger list).

Alternative solutions

I did not see any way to query the schedule info but please let me know if I am missing something!

Activity

  1. cchensh commented on Sep 10, 2025

    @cchensh
    Contributor

    Thank you @brahn , this is a great suggestion. From the backend perspective, we should be able to fetch the next expected run time but we might need to surface that info with the triggers.list API. @zimeg , I believe this is the right approach but please let me know if you have different ideas 🙏

  2. added
    enhancementM-T: A feature request for new functionality
    server side issueAn issue that exists on the Slack Platform, Slack API, or other remote endpoint
    on Sep 10, 2025
  3. zimeg commented on Sep 10, 2025

    @zimeg
    Member

    From the backend perspective, we should be able to fetch the next expected run time but we might need to surface that info with the triggers.list API.

    @cchensh This is a great approach IMHO! I'm not sure if these details are surfaced elsewhere at the moment, but this is where I might expect to find such.

    I am noticing that workflows.triggers.list method returns the following but am unsure if this is related to the trigger scheduling:

    {
      "id": "Ft09E7FVBBHD",
      "workflow": {
        "id": "Fn09E7FU9C31",
        "date_created": 1757545924,
        "date_released": 0,
        "date_updated": 1757545947,
        "date_deleted": 0,
        "form_enabled": false,
        "workflow_id": "Wf09E7FU9JS3"
      }
    }

    For now I'll mark this as an enhancement but am unsure of the database changes needed to support this on the backend at this time 🤖

  4. removed their assignment
    on Jan 21, 2026
  5. added
    area:deno-sdkRelated to github.com/slackapi/deno-slack-sdk
    on Feb 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:deno-sdkRelated to github.com/slackapi/deno-slack-sdkenhancementM-T: A feature request for new functionalityserver side issueAn issue that exists on the Slack Platform, Slack API, or other remote endpoint

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions