Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-2478

Billabe Usage Remittance records not updating with retry_after on failure.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 2024-06-12 - API
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • True
    • 5

      While testing in prod we encountered the below logs. This is expected because we had duplicate subscriptions for azure at the time, however the retry_after column was not populated and the billable usage messages were never resent.

      We need to make sure messages are being published and consumed correctly from the billable-usage.dlt topic.

      Skipping billable usage with id=b991ae87-dfd4-403d-b343-fe2d125b85c8 orgId=17691289 because the subscription was not found. Will retry again after one hour.

       

              kflahert@redhat.com Kevin Flaherty
              kflahert@redhat.com Kevin Flaherty
              Aurobinda Nayak Aurobinda Nayak
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: