I'm looking for copies of Urbanairship invoices - are they to be found under "Payment History" in our account? This link is broken at the moment

Didn't find what you were looking for?

New post

Comments

6 comments

  • Hi Matt,

    Yes, your invoices can be found under the "Payment History" page.

    If that page is not loading for you, can you give me a screenshot of the broken link at all? I can see if I can find what the issue is.

     

    Comment actions Permalink
    0
  • Hi Michael - this is what we get 

    Comment actions Permalink
    0
  • Thanks Matt.

    Would you be able to provide me with the Web Console logs of that page? You can get to this by right-clicking on the page and clicking the "inspect" options. There will be console logs that will show what errors that page is running into.

    Comment actions Permalink
    0
  • Here you go:

    https://go.urbanairship.com/accounts/payment/-/invoices/?limit=12 500 (Internal Server Error)
    t @ index.js:44
    n @ index.js:34
    e @ stream.js:13
    f.write @ index.js:26
    (anonymous) @ invoice-modal.js:49
    n.emit @ events.js:78
    o.open @ index.js:132
    t @ stripe-payment.js:68
    ge @ ractive.runtime.js:2486
    ve @ ractive.runtime.js:2452
    pe @ ractive.runtime.js:2436
    hn @ ractive.runtime.js:8307
    yn @ ractive.runtime.js:8463
    index.js:44 Fetch complete: GET "https://go.urbanairship.com/accounts/payment/-/invoices/?limit=12".
    t @ index.js:44
    n @ index.js:34
    e @ stream.js:13
    f.write @ index.js:26
    (anonymous) @ invoice-modal.js:49
    n.emit @ events.js:78
    o.open @ index.js:132
    t @ stripe-payment.js:68
    ge @ ractive.runtime.js:2486
    ve @ ractive.runtime.js:2452
    pe @ ractive.runtime.js:2436
    hn @ ractive.runtime.js:8307
    yn @ ractive.runtime.js:8463

    Comment actions Permalink
    0
  • Matt,

    I am escalating this issue to our Engineering team, so they'll be investigating this issue. As soon as I receive an update from them, I will let you know!

    Comment actions Permalink
    0
  • Matt,

    Apologies for the delay on getting back to you on this. I've heard from our Engineering team that this error should now be resolved. Could you check on your end to see if you still experience this issue?

    Comment actions Permalink
    0

Please sign in to leave a comment.