You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE] scheduled triggers: display schedule (including next run time) in CLI-echoed info #226
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!
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 🙏
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:
Activity
cchensh commentedon Sep 10, 2025
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 🙏
zimeg commentedon Sep 10, 2025
@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.listmethod 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 🤖