Skip to content

Keep failed transaction lines eligible for retry - #793

Merged
StuartFerguson merged 3 commits into
mainfrom
task/#790_tighten_up_line_processing
Sep 16, 2026
Merged

StuartFerguson merged 3 commits into
mainfrom
task/#790_tighten_up_line_processing

Conversation

@StuartFerguson

Copy link
Copy Markdown
Member

Summary

  • Leave file lines unchanged when transaction dispatch fails, allowing the workflow to retry them.
  • Capture each transaction number once and format it invariantly for dispatch.
  • Add tests for dispatch failures, timeouts, and stable file line identity across retries.

Testing

  • Added unit tests covering failure and retry behavior.

@codacy-production

codacy-production Bot commented Sep 16, 2026 •

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 14 complexity · 0 duplication

Metric Results
Complexity 14
Duplication 0

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 02d20f3d54

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ensure the send to transaction processor is watertight

1 participant