Skip to main content
Solved

Push Notificaions Error "More than 1 inserted or deleted row mathed"?


Forum|alt.badge.img+5
  • Captain II
  • 398 replies

Hello,

  I see some errors on system monitor:

When I go to Process push notifications, yes , there are also errors.

 

I did NOT configure or Activated any push notifications. 

 

My question:

1, What is this all about? I did not configure to send notifications why it is kept sending?

2, how can I stop these errors? I don’t know what are them for. I don’t need them.

Best answer by rosenjon

@dmurray I’m certainly no expert on any of this, but I have peaked under the hood of the Acumatica Framework a bit. Acumatica has been making more extensive use of SignalR Hubs in recent releases. I wouldn’t be surprised if what you’re seeing is a failure related to an internal messaging process, rather than one you setup yourself. The term “push notification” is kind of a catch-all end user term that could describe a lot of different things. However, I think the underlying technology that enables it is mostly based on SignalR (and in previous releases MSMQ). It’s not clear that the error you’re pointing out is a hard failure, as opposed to an informational message from the logging process attached to the the SignalR Hub saying “I cannot disambiguate the information I’m getting, so I’m not going to try to log this information”).

View original
Did this topic help you find an answer to your question?

4 replies

Forum|alt.badge.img+5
  • Author
  • Captain II
  • 398 replies
  • January 29, 2021

Hello,

    I cleared all errors and monitor 1 step by step.
I found the error happens when I am saving a new payment with invoice to apply.

   So my question turns to
 Why it would trigger a push notification when I am saving a payment?


  • Jr Varsity III
  • 18 replies
  • January 4, 2023

I just fell down the same rabbit hole. I discovered this trying to track down why so many resources were going into Push Notifications via a Long Running Process.

 

My paranoid side was worried this might be some built-in webhook to extract our data to the mother ship. I would hope this is not the case.

 

The more likely culprit seems to be failed Business Event logic, I can’t find much if any documentation, but it seems that Business Events “Trigger by Record Change” uses this system level “Business Process” Push Notifications to “trigger” said event.

  1. If this is the case, can we get the errors pushed up to our Business Events?
  2. Can we get some expanded documentation on this Push Notification Destination that doesn’t exist in our defined Push Notifications?
  3. Can we get elaboration on “More than one inserted or deleted row matched”? My only Business Event on the page in question tracks the change of one field (Status), I wouldn’t care about any Inserted or Deleted records.

 

@Chris Hackett can you point us to the right person for a response here?


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • 2621 replies
  • January 4, 2023

Hi @dmurray - we need to rely on our experts here to chime in. I am not sure who that might be. As this post is rather old, if you don’t get response you may consider posting a new question and referencing this post. Thank you


Forum|alt.badge.img+5
  • Semi-Pro III
  • 293 replies
  • Answer
  • January 22, 2023

@dmurray I’m certainly no expert on any of this, but I have peaked under the hood of the Acumatica Framework a bit. Acumatica has been making more extensive use of SignalR Hubs in recent releases. I wouldn’t be surprised if what you’re seeing is a failure related to an internal messaging process, rather than one you setup yourself. The term “push notification” is kind of a catch-all end user term that could describe a lot of different things. However, I think the underlying technology that enables it is mostly based on SignalR (and in previous releases MSMQ). It’s not clear that the error you’re pointing out is a hard failure, as opposed to an informational message from the logging process attached to the the SignalR Hub saying “I cannot disambiguate the information I’m getting, so I’m not going to try to log this information”).


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings