Understanding Monthly Table Scheduling and Tracking Run Times

Siddhant B. · 2025-04-25 17:48:51.03781+00

If I set this table to run every month, does it mean that it will run it once right now and then after a month? Can I see somewhere what date/time it has been set to in order to avoid confusion and for me to check whether it runs it successfully after that time?

Understanding Monthly Table Scheduling and Tracking Run Times | Clay

8 comments

· Sorted by Oldest

Channeled
APP
·
·
When you set a table to run monthly, it won't run immediately. The schedule will start from the moment you set it up, and the first run will occur one month from that date. Unfortunately, our current sources don't mention a specific way to check the exact date and time for the next scheduled run or verify its successful execution. However, you can monitor your table for updates after the expected run date to confirm if the scheduled run was successful. If you need more detailed information about scheduling or run verification, you might want to request human assistance for further guidance.
Sources: Build a sustainable growth engine with Scheduling - The GTM with Clay Blog Scheduled columns | Documentation | Clay University Scheduled columns | Documentation | Clay University
Channeled
APP
·
·
Siddhant B.
·
·
I don't think the automated response is correct. I think it runs fully once "now" and then at the time interval specified.
Smit V.
·
·
Hi Siddhant, thank you for reaching out! When you schedule a table to run, it executes according to the interval you’ve set-in your case, once a month. This means it will only run at the scheduled time, not immediately upon scheduling. Could you share what made you think the table might also run immediately? I’d be happy to clarify further or assist with anything else! Let me know how I can help :)
Siddhant B.
·
·
It did run but after a while. I assume it would have been scheduled at the backend. I came back to the table the next day and all the rows had executed. I didn't manually run them (since I expected this behavior).
Bo (.
·
·
Siddhant - Do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Siddhant B.
·
·
https://app.clay.com/workspaces/39601/tables/t_aIptFogP0WM2/views/gv_5NnnfpouJDOd
Owen C.
·
·
Hey Siddhant, thanks for reaching out! As of right now there isn't a direct way to set the date and time for when something will run. However, when you setup a signal for example job changers and set a window of time to search historically (i.e. 3months) the signal will update now (search for anyone who's changed jobs in the last three months) and then update on the cadence you've set. Let me know if this makes sense and how else we can help!

Channeled
APP
·
·
When you set a table to run monthly, it won't run immediately. The schedule will start from the moment you set it up, and the first run will occur one month from that date. Unfortunately, our current sources don't mention a specific way to check the exact date and time for the next scheduled run or verify its successful execution. However, you can monitor your table for updates after the expected run date to confirm if the scheduled run was successful. If you need more detailed information about scheduling or run verification, you might want to request human assistance for further guidance.
Sources: Build a sustainable growth engine with Scheduling - The GTM with Clay Blog Scheduled columns | Documentation | Clay University Scheduled columns | Documentation | Clay University
Channeled
APP
·
·
Siddhant B.
·
·
I don't think the automated response is correct. I think it runs fully once "now" and then at the time interval specified.
Smit V.
·
·
Hi Siddhant, thank you for reaching out! When you schedule a table to run, it executes according to the interval you’ve set-in your case, once a month. This means it will only run at the scheduled time, not immediately upon scheduling. Could you share what made you think the table might also run immediately? I’d be happy to clarify further or assist with anything else! Let me know how I can help :)
Siddhant B.
·
·
It did run but after a while. I assume it would have been scheduled at the backend. I came back to the table the next day and all the rows had executed. I didn't manually run them (since I expected this behavior).
Bo (.
·
·
Siddhant - Do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Siddhant B.
·
·
https://app.clay.com/workspaces/39601/tables/t_aIptFogP0WM2/views/gv_5NnnfpouJDOd
Owen C.
·
·
Hey Siddhant, thanks for reaching out! As of right now there isn't a direct way to set the date and time for when something will run. However, when you setup a signal for example job changers and set a window of time to search historically (i.e. 3months) the signal will update now (search for anyone who's changed jobs in the last three months) and then update on the cadence you've set. Let me know if this makes sense and how else we can help!