New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webhook not working #1750
Comments
Hi Rodrigo, There were no any changes related to webhook functionality for the last year or so. |
Thanks for the info Yuri.
It was working before. Any clue how to debug this?
With DEBUG enable, I'm getting only this on the Logs
[2020-07-01 14:13:02] Espo.DEBUG: BPM: processPendingFlows [] []
[2020-07-01 14:13:02] Espo.DEBUG: BPM: processTriggeredSignals [] []
*[2020-07-01 14:14:02] Espo.INFO: CronManager: Stop cron running, too
frequent execution. [] []*[2020-07-01 14:14:03] Espo.DEBUG: BPM:
processPendingFlows [] []
[2020-07-01 14:14:03] Espo.DEBUG: BPM: processTriggeredSignals [] []
*[2020-07-01 14:15:02] Espo.INFO: CronManager: Stop cron running, too
frequent execution. [] []*[2020-07-01 14:15:03] Espo.DEBUG: BPM:
processPendingFlows [] []
[2020-07-01 14:15:03] Espo.DEBUG: BPM: processTriggeredSignals [] []
[2020-07-01 14:16:02] Espo.DEBUG: BPM: processPendingFlows [] []
[2020-07-01 14:16:02] Espo.DEBUG: BPM: processTriggeredSignals [] []
*[2020-07-01 14:17:01] Espo.INFO: CronManager: Stop cron running, too
frequent execution. [] []*[2020-07-01 14:17:02] Espo.DEBUG: BPM:
processPendingFlows [] []
[2020-07-01 14:17:02] Espo.DEBUG: BPM: processTriggeredSignals [] []
But even with these messages, on the Scheduled Jobs, the webhooks are
getting done each minute.
Thanks
Em qua., 1 de jul. de 2020 às 02:44, Yuri Kuznetsov <
notifications@github.com> escreveu:
… Hi Rodrigo,
There were no any changes related to webhook functionality for the last
year or so.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1750 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUXTGVWLVHQ3T7ZNRVWJTDRZLEKDANCNFSM4OMVCQAA>
.
|
Please help, the debug is not informing any problem. [2020-07-02 20:18:36] Espo.DEBUG: Workflow\Actions: Start [updateEntity] with cid [0] for entity [GoogleSheets, 5efe2de88a1bce4e9]. [] [] you can see my workflow, but nothing about the Webhook. |
I tested and it worked fine on the latest version. I will be absent for 5 days or so. Suggest debugging in
|
Thanks for trying to help Yuri.
I'm really lost. I tried to put the Debug lines you mentioned on the
Sender.php of Webhook folder, but nothing happened on the log as well.
I think the webhook is not being called. And I have no idea why.
Em sex., 3 de jul. de 2020 às 01:11, Yuri Kuznetsov <
notifications@github.com> escreveu:
… I tested and it worked fine on the latest version. I will be absent for 5
days or so. Suggest debugging in application/Espo/Core/Webhook. You can
add log lines:
$GLOBALS['log']->debug('Some text');
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1750 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUXTGU2MIUF2MLIPDBIGSTRZVK7TANCNFSM4OMVCQAA>
.
|
Check whether the scheduled job is running. |
I don't know what to do anymore. Thanks |
Check 2 |
Hi Yuri, thanks for trying to help. I'm doing my best, but, please, tell me
which line of code I have to put in there for Debugging.
Thanks.
Em qui., 16 de jul. de 2020 às 04:25, Yuri Kuznetsov <
notifications@github.com> escreveu:
… Try to debug here:
https://github.com/espocrm/espocrm/blob/stable/application/Espo/Hooks/Common/Webhook.php#L55
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1750 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUXTGVREV4MMHFEVSXOMC3R32TPHANCNFSM4OMVCQAA>
.
|
@yurikuzn , after restarting Apache and PHP, the webhook started working again. |
Does it execute afterSave? Is your debug logged? |
Yes, after restarting, it is debbuging. Take a look below. [2020-07-16 15:16:33] Espo.DEBUG: Debugging WEBHOOK [] [] |
Right now, I just created a new record, and it didn't push via webhook. Very weird. apparently, it is doing a LOOPING on webhook, I don't know why, and stopping at middle, as you can see on the log below. I'm doing only 1 saving, and it gives a LOT of calls on the AFTERSAVE [2020-07-16 15:23:48] Espo.DEBUG: Debugging WEBHOOK [] [] |
It supposed to be called multiple times. It's not looping. |
what about this line? |
I don't know. Debug deeper. Webhook manager class > process methods. Check whether they are executed on record save. Check The logic of webhooks is not that hard. You could analyze the code, add debug logging to figure out where it fails. |
@yurikuzn , after some time trying to find why it is working sporadically, I found that if I ask to REBUILD BACKEND, it start to work again, and, after some hours, stops again. I don't know if this info helps to find the cause. In a desperate trial, yesterday I upgrade the system from Ubuntu 18.04 to Ubuntu 20.4, but, even with newer packages and libraries, the same error is happening. No idea anymore.... |
So, @yurikuzn , please, since I CONFIRMED that it starts working again after asking to REBUILD BACKEND, and stops again after some hours, at least I can put on cron to rebuild it from time to time. Thanks. |
Nothing (must nothing)
Try this: NOTE: If the problem cannot reproduced with the fresh copy of crm then it is most probably not related to espocrm itself. |
Thank you so much @eymen-elkum. Are you working on EspoCRM. Kind regards, |
Yes, I am working on new extensions. |
Great. Good to know. Best for you.
Em ter., 4 de ago. de 2020 às 13:08, Eymen Elkum <notifications@github.com>
escreveu:
… Are you working on EspoCRM
Yes
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1750 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUXTGUTP7FP53UOGV46X33R7AW7VANCNFSM4OMVCQAA>
.
|
Hi, webhooks that were working on previous versions are not working anymore.
Anyone else with problems?
The text was updated successfully, but these errors were encountered: