Add Scheduled Actions

[ilikesymmetry]

📼 Feature demo

Note that you can demo this app on the preview URL, but the finest granularity we get for free is refreshes every 5 minutes!

What's included in this pr + description

• adds scheduling to fungible token transfer action
• schedules enable setting a repeating cycle to generate new checks automatically as an effort to save manual labor time on writing new checks periodically for signers
• this pattern mimics salary-like payments (e.g. Justworks pays us every two weeks until we tell it to stop)

Schedule parameters:

• start date: when will this schedule start executing
• period unit: enum for the delay between cycles (weeks/months, minutes included for dev testing)
• period coefficient: number to multiple with unit to get total period cycle the action repeats on
• max count: number of cycles to run

Motivation & Context

• helps teams automate action definition to reduce effort for signers

Steps to test

📼 Local set up guide

create

1. Create schedule -> see new check created and new schedule created in respective tabs
2. Wait for next refresh at time to come and then see new schedule!
3. Wait for counter to reach max count and then refreshing stops

edit

1. Create schedule
2. Changing schedule period doesn't change next refresh if we have not started yet
3. Change schedule period (change one or both of coefficient or unit in "repeats every" question) -> next refresh time is new period applied to last refresh time

Screenshots and/or loom video

Logs showing retry attempts by Upstash in case of failure or running out of time from Vercel killing process, 4 retries are made before giving up

Outstanding issues

• should we not create a check right now if they set start date into the future / only create check if start is right now?
• logic of editing a schedule while in the middle of its execution is a bit wonky
• thinking we want to disable editing a schedule that has already completed because edit logic gets harder to set next refresh time

Relevant docs

• https://vercel.com/guides/how-to-setup-cron-jobs-on-vercel#high-frequency-cron-jobs

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
web	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Feb 7, 2023 at 5:54PM (UTC)

[kristencheung]

I have ngrok running locally and looks like it's pinging the api, but for some reason though it's not creating a check.

I have it running per minute, the first check is created, but the subsequent checks aren't created, the progress counter isn't incremented, and the schedule isn't refreshed 🤔

Trying to explore if something went wrong with the setup / gonna try digging into the code to see why it's not working properly..

Edit: okay following up, I spent too long to then figure out I didn't watch the end of the loom to know that I also needed to add the qstash env variables 🙈

[mcgingras]

progress is 2/3 despite all three having been scheduled?

queued 4 despite only being out of 3

[kristencheung]

edge case, but if multiple schedules are synced looks like there can be some nonce collisions

[mcgingras]

pushing a commit to remove unused imports

[kristencheung]

Yayyy! nice job setting this up 👏 left a couple of comments, and avoided ux comments since we're going to be moving to a new repo with new designs anyways.

should we not create a check right now if they set start date into the future / only create check if start is right now?

Yes^ that's the expected behavior

logic of editing a schedule while in the middle of its execution is a bit wonky

Worked for me! are there any known edge cases that are outstanding?

thinking we want to disable editing a schedule that has already completed because edit logic gets harder to set next refresh time Agree, we should disable editing after schedule is expired and allow users to archive expired schedules

[kristencheung]

pushing a commit to remove unused imports

reminder to add eslint-plugin-unused-imports to our next repo haha