eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions

Fix job search schedule (daily 4 AM, not hourly) and note 200 req/month free tier

Browse source 
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Erich Blume 2026-03-08 11:45:03 -07:00
commit 7bec288d20
2 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/how-to/jobsync/deploy-jobsync.md
View file

@ -63,7 +63,7 @@ JobSync has no metrics endpoint. Logs are collected by Alloy on ringtail and shi
{namespace="jobsync", app="jobsync"}
```
The app runs a scheduled job search hourly (cron `0 * * * *`). Search failures appear in logs during those executions.
The app runs a scheduled job search daily at 4 AM. Search failures appear in logs during those executions.
## Related

4
docs/reference/services/jobsync.md
View file

@ -55,7 +55,7 @@ The automated job search feature uses the [JSearch API](https://rapidapi.com/let
Without either, job search automations fail with: `Search failed: network - RAPIDAPI_KEY is not configured`
The key is stored in 1Password ("JobSync" item, `rapidapi_key` field) and synced via ExternalSecret.
The free tier allows 200 requests/month. The key is stored in 1Password ("JobSync" item, `rapidapi_key` field) and synced via ExternalSecret.
## Secrets
@ -83,7 +83,7 @@ To search for job search errors specifically:
{namespace="jobsync", app="jobsync"} |~ "(?i)(rapid|search failed|error)"
```
The app runs a scheduled job search every hour (cron `0 * * * *`). Failures appear in logs during those executions.
The app runs a scheduled job search daily at 4 AM. Failures appear in logs during those executions.
## Container