starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Implement django-rq retry mechanism #7936

New Issue
Closed
opened 2025-12-29 20:30:14 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:30:14 +01:00
Owner
Copy Link

Originally created by @abhi1693 on GitHub (Apr 22, 2023).

Originally assigned to: @abhi1693 on GitHub.

NetBox version

v3.4.8

Feature type

New functionality

Proposed functionality

Link: https://python-rq.org/docs/exceptions/

It would be best if the jobs can have exponential retries that finally fails after 3 days. To have it retry for that long and still fail, would be on the users to figure out how to get the data that they missed.

Use case

When I create webhooks, there are times when the receiver is down and then the webhooks are missed. When the receiver comes online, it does not receive the changes. To overcome this, we have to build extra workarounds to find the data that got missed during the downtime and the webhook trigger again.

With an exponential retry mechanism, such issues can be avoided to a lot of extent.

Database changes

No response

External dependencies

No response

Originally created by @abhi1693 on GitHub (Apr 22, 2023). Originally assigned to: @abhi1693 on GitHub. ### NetBox version v3.4.8 ### Feature type New functionality ### Proposed functionality Link: https://python-rq.org/docs/exceptions/ It would be best if the jobs can have exponential retries that finally fails after 3 days. To have it retry for that long and still fail, would be on the users to figure out how to get the data that they missed. ### Use case When I create webhooks, there are times when the receiver is down and then the webhooks are missed. When the receiver comes online, it does not receive the changes. To overcome this, we have to build extra workarounds to find the data that got missed during the downtime and the webhook trigger again. With an exponential retry mechanism, such issues can be avoided to a lot of extent. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 20:30:14 +01:00
adam closed this issue 2025-12-29 20:30:15 +01:00
adam commented 2025-12-29 20:30:15 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (May 8, 2023):

@jeremystretch Is this alright, if I introduce new configuration that manages the retry related configurations? I think that would provide the most user friendly solution.

@abhi1693 commented on GitHub (May 8, 2023): @jeremystretch Is this alright, if I introduce new configuration that manages the retry related configurations? I think that would provide the most user friendly solution.
adam commented 2025-12-29 20:30:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 10, 2023):

@abhi1693 without digging into this myself it's hard to know what would be needed, but I'm not opposed to it.

@jeremystretch commented on GitHub (May 10, 2023): @abhi1693 without digging into this myself it's hard to know what would be needed, but I'm not opposed to it.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7936
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?