Sync: doesn't map `cron_cursor_job_id`
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
openfn project pull seems to not hadle cron_cursor_job_id properly, leaving a UUID in the workflow.yaml rather than an id.
This needs to be mapped at pull and deploy time.
Eg
id: my-workflow
name: my workflow
start: cron
steps:
- id: a
name: A
adaptor: '@openfn/language-http@7.0.3'
expression: ./a.js
- id: cron
type: cron
enabled: false
cron_expression: '*/15 * * * *'
cron_cursor_job_id: f3f65918-9804-46f4-8778-032acac8db37
next:
a:
disabled: false
condition: always
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the openfn project pull and deploy entry points, then trace how cron_cursor_job_id is read and written in workflow.yaml. Reproduce the example workflow and verify that pull and deploy both map the UUID to the expected ID rather than leaving it unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100