You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When there is a job id available due to an error, there is no way to look up what message and channel this job belongs to. This causes us to look up the data in the DB directly, which we would ideally want to avoid.
Describe the solution you'd like
A endpoint that exposes the Job details and links to the message, channel, consumer and producer.
Describe alternatives you've considered
The obvious alternate considered is to inspect DB; or alternatively we could create a Webhook Broker CLI that would allow easy inspection of the queue.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When there is a job id available due to an error, there is no way to look up what message and channel this job belongs to. This causes us to look up the data in the DB directly, which we would ideally want to avoid.
Describe the solution you'd like
A endpoint that exposes the Job details and links to the message, channel, consumer and producer.
Describe alternatives you've considered
The obvious alternate considered is to inspect DB; or alternatively we could create a Webhook Broker CLI that would allow easy inspection of the queue.
Additional context
N/A
The text was updated successfully, but these errors were encountered: