MokoConsulting/MokoJoomCross
1
0
Fork 0
Code Issues 105 Pull Requests Releases 1 Wiki Activity

Retry mechanism for failed posts #51

New Issue
Open
opened 2026-05-29 02:08:14 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-29 02:08:14 +00:00
Owner
Copy Link
Copy Source

Summary

Failed cross-posts currently sit in the queue with error status. Add automatic and manual retry with backoff.

Acceptance Criteria

  • Task plugin auto-retries failed posts up to N times (configurable, default 3)
  • Exponential backoff between retries (5m, 30m, 2h)
  • Admin can manually retry individual failed posts
  • Admin can bulk-retry all failed posts for a service
  • After max retries, post moves to permanently_failed status with notification
## Summary Failed cross-posts currently sit in the queue with error status. Add automatic and manual retry with backoff. ## Acceptance Criteria - Task plugin auto-retries failed posts up to N times (configurable, default 3) - Exponential backoff between retries (5m, 30m, 2h) - Admin can manually retry individual failed posts - Admin can bulk-retry all failed posts for a service - After max retries, post moves to `permanently_failed` status with notification
jmiller commented 2026-05-29 02:08:16 +00:00
Author
Owner
Copy Link
Copy Source

Branch created: feature/51-retry-mechanism-for-failed-posts

git fetch origin
git checkout feature/51-retry-mechanism-for-failed-posts
Branch created: [`feature/51-retry-mechanism-for-failed-posts`](https://git.mokoconsulting.tech/MokoConsulting/MokoJoomCross/src/branch/feature/51-retry-mechanism-for-failed-posts) ```bash git fetch origin git checkout feature/51-retry-mechanism-for-failed-posts ```
Sign in to join this conversation.
Labels
Clear labels
pending: testing
Implemented, awaiting testing
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels
Type Feature
Status —
Priority High
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoJoomCross#51
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?