Cron Jobs: Update long-running PLC job schedule

[molly-moen]

We had the below honeybadger errors due to process_pd_workshop_ends, sync_dropbox and fill_jotform_placeholders having too quick of schedules--the scripts were trying to run multiple times at once. All were previously running every minute. Updated process_pd_workshop_ends to run every 2 minutes instead of every minute, and updated fill_jotform_placeholder to run every 5 minutes, as we now have very few JotForm surveys and the results do not need to be immediately available. sync_dropbox has a "total time" constant in the script which was set to 60 - update interval, so it would occasionally run over time. Updated that script to have a 5 second buffer.

Links

• process_pd_workshop_ends error
• fill_jotform_placeholders error
• sync_dropbox error

Reviewer Checklist:

• Tests provide adequate coverage
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked

[bencodeorg]

First two changes look good, but I think the sync_dropbox one might be good to keep at a minute. The script actually runs another command that syncs changes from Dropbox to our staging instance every 5 seconds, which gives almost real time feedback to content editors. This would result in half of the time having changes take up to a minute to show up in staging, which I feel could be annoying.

I think the fix might be to dial down the TOTAL_SECONDS = 60 - INTERVAL_SECONDS here to maybe 55 - INTERVAL_SECONDS, which hopefully will give enough room for the script to complete before the minute mark?

[bencodeorg]

Thanks for doing this!

[breville]

@bencodeorg nice catch on maintaining the editor experience. And thanks @molly-moen for the broader fix.