Improved notifications and recovery for target failures

2 コメント

  • Jason Kadlec
    コメントアクション Permalink

    YES!!! How are more people not blowing up this thread??!?!


    We have records of failed attempts - where the attempt was sent to a Redis based queue - pretty much the lightest thing our server to do.

    At the time stamp of the "failed attempt" - we have NO record of any downtime, errors or anything close to a maxed out CPU/Memory etc.


    WE NEED LOGS!!! 


    I would love all the same things Collin has requested, but I would start the list at #3, and put the link and the response platforms at the bottom of the list.


    We need, need, need logs so we know why something failed, and logs while it is disabled so we can back-fill manually.





  • Nathan Stowe
    コメントアクション Permalink

    Just got this error but there are no failures saved under my Channels > API > Target Failures section. :(



Powered by Zendesk