Skip to content

Commit dce2266

Browse files
committed
docs(spec): the F2 D3 entry says migrate meta lists only blocks that omit the count
Claude-Session: https://claude.ai/code/session_01MT2aGLQQhH8ZsPrgqHMrwz Co-authored-by: Claude <noreply@anthropic.com>
1 parent 0bc4f42 commit dce2266

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

‎packages/spec/src/migrations/entries/semantic/18.job-retry-policy-without-attempts-refused.ts‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,8 +24,10 @@ export const entry: SemanticMigration = {
2424
+ 'at `retryPolicy.maxRetries` instead, at `objectstack validate`, `objectstack build` and '
2525
+ '`defineStack`, so under `objectstack lint` too when the config calls it: "a retry block with no '
2626
+ 'attempts is no retry block". The D2 conversion makes the 17 edit wherever the chain '
27-
+ 'reaches: `objectstack migrate meta` lists every such block in your metadata sources and writes '
28-
+ 'both pre-17 numbers into it, which keeps the retries the job ran with. Stored jobs keep loading '
27+
+ 'reaches: `objectstack migrate meta` lists every block in your metadata sources that omits the '
28+
+ 'count and writes both pre-17 numbers into it, which keeps the retries the job ran with; a block '
29+
+ 'that writes `maxRetries: 0` it does not list, and you delete that block by hand (or state a '
30+
+ 'count). Stored jobs keep loading '
2931
+ 'with the same numbers, because every rehydration seam replays the conversion. Decide per job: '
3032
+ 'keep the written count, or delete the block if the job should run once. A block that already '
3133
+ 'states `maxRetries` and omits `backoffMultiplier` is not refused, and its delay is now flat '

0 commit comments

Comments
 (0)