midime80
commented
3 months ago More testing was needed... :)... It does work... the GB-aanvuller is only allowed to be requested IF the data is at 80%... And when the first 20GB is done then the 80% is related to 2GB... so when 400MB is left then it's allowed to get GB-Aanvuller...
Sorry... and Thanks! :)
The first time when the 80% message comes it works flawless.
But the second message from ODIDO refers to slowdown the speed unless the GB-aanvuller is used. When i changed in the flow to respond on that message too, it works to follow the flow and sent a request... but it goes wrong... it gives back the response code 500. And when the first message was sent it got response code 202.
What goes wrong here...?
07-27 07:31:34.156 I 11@28: Expression true? 07-27 07:31:34.157 U 11@29: Received message containing the keyword "verbruikt" 07-27 07:31:34.157 I 11@38: Failure catch 07-27 07:31:34.158 I 11@12: HTTP request 07-27 07:31:34.911 I 11@13: Variable set 07-27 07:31:34.912 U 11@14: Your linkedsubscription API url: https://capi.odido.nl/XXXXX/linkedsubscriptions 07-27 07:31:34.912 I 11@41: Failure catch 07-27 07:31:34.912 U 11@44: Your linkedsubscription API url: https://capi.odido.nl/XXXXX/linkedsubscriptions 07-27 07:31:34.913 I 11@31: HTTP request 07-27 07:31:37.973 I 11@32: Variable set 07-27 07:31:37.975 U 11@33: Your subscribtion API url: https://capi.odido.nl/XXXXX/customer/XXXXX/subscription/XXXXX 07-27 07:31:37.975 I 11@24: Atomic store 07-27 07:31:37.980 I 11@42: Failure catch 07-27 07:31:37.980 I 11@16: HTTP request 07-27 07:31:38.547 U 11@18: Your add bundle response code: 500 07-27 07:31:38.547 I 11@27: SMS received
The numbers where replaced by > XXXXX.