YetiForceCRM
YetiForceCRM copied to clipboard
YetiForceCompany
WF not working
trying to create a email history record to convert into a lead record,, cant understand what is wrong.. can anyone help.. cron executes fine....but leads not created....
YF version 6.1.0 upgraded from 5.3 to 6.0
please see all screenshots...
can this help :
2020-12-02 15:45:03 | Start CRON ---------- 2020-12-02 15:45:03 | LBL_WORKFLOW - Not ready to run as the time to run again is not completed 2020-12-02 15:45:03 | LBL_SCHEDULED_IMPORT - Start task 2020-12-02 15:45:03 | LBL_SCHEDULED_IMPORT - End task (0.13 s) 2020-12-02 15:45:03 | LBL_MAIL_SCANNER_ACTION - Start task 2020-12-02 15:45:12 | LBL_MAIL_SCANNER_ACTION - End task (8.72 s) 2020-12-02 15:45:12 | LBL_MAIL_SCANNER_VERIFICATION - Start task 2020-12-02 15:45:12 | LBL_MAIL_SCANNER_VERIFICATION - End task (0.09 s) 2020-12-02 15:45:12 | LBL_MAIL_SCANNER_BIND - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_MAILER - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_CARD_DAV - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_CAL_DAV - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_ACTIVITY_STATE - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_SEND_REMINDER - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_SEND_NOTIFICATIONS - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_MULTI_REFERENCE_VALUE - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_CRMACTIVITY_DAYS - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_ASSETS_RENEWAL - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_SOLD_SERVICES_RENEWAL - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_RECORD_LABEL_UPDATER - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_PRIVILEGES_UPDATER - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_ADDRESS_BOOK - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_MARK_RECORDS_AS_REVIEWED - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_NEVER_ENDING_RECURRING_EVENTS - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_CACHE - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_CLEAR_FILE_UPLOAD_TEMP - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_SMSNOTIFIER - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_BROWSING_HISTORY - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBK_SYSTEM_WARNINGS - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_BATCH_PROCESSES - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_BATCH_METHODS - Start task 2020-12-02 15:45:12 | LBL_BATCH_METHODS - End task (0 s) 2020-12-02 15:45:12 | LBL_SESSION_CLEANER - Start task 2020-12-02 15:45:12 | LBL_SESSION_CLEANER - End task (0.03 s) 2020-12-02 15:45:12 | LBL_CURRENCY_UPDATE - Not ready to run as the time to run again is not completed 2020-12-02 15:45:12 | LBL_MAIL_RBL - Not ready to run as the time to run again is not completed =============== 2020-12-02 15:45:12 (9.15) | End CRON ==========
@mariuszkrzaczkowski what does : " Not ready to run as the time to run again is not completed"? means just help me with that i shall find a solution
@rioshaz this means what previous task not fully completed at new cron start attempt
or it crashed because there was an error, but there is no full information, so it's hard to say something
@mariuszkrzaczkowski @vovpff no tt means that the time for it to run again hasnt been completed yet.. example my cron is set to run every 5 minutes and services which have a frequency of more than 5 minutes like LBL_MAIL_SCANNER_BIND (it has 10 min frequency) will show " Not ready to run as the time to run again is not completed""
so i suppose my crons are working fine but scanner don't add emails to tickets module, in 5.3 it was working dine..
i tried with a fresh new installation of 6.0 and it added 2 emails but since then not adding emails to tickets anymore..
strange,,,
@mariuszkrzaczkowski I have sent a test email to your gmail id : [email protected] and have also set your email in the mail scanner to create the helpdesk (ticket record)... pls see screenshot... but even after your cron has ran the ticket is not being created...
and i have tested all this on your gitstable version..
so can u pls investigate and help me if possible,,, thanks a lot sir..
Please use... wget ...root/cron.php - work fine...
Użyj np wget zamiast uruchamiać crona z cron.sh U mnie zadziałało...
cron ---> wget --delete-after http://xxxxx.xx/cron.php?app_key=from_config_file
config/main.php /** Unique Application Key */ public static $application_unique_key = '...........'
trying to create a email history record to convert into a lead record,, cant understand what is wrong.. can anyone help.. cron executes fine....but leads not created....
YF version 6.1.0 upgraded from 5.3 to 6.0
please see all screenshots...
@zimart did the wget command but still this workflow dont work, other workflow works.. is something wrong with this workfow ?
@mariuszkrzaczkowsk have tested on gitdeveloper too but the same workflow is not working... email history to lead .. please check sir
I can confirm the problem with the mailscanner:
I have configured the actions "New e-Mail" and "New ticket in Helpdesk" and there are no new tickets listed, when the e-mail was not read before. Cron jobs are running an executed.
I am running latest YetiForce CRM 6.1 Service Pack v7. With V. 5.3 SP4 it was working. After the upgrade it is not working any more.
Sorry, wrong issue. I was refering to this issue here: https://github.com/YetiForceCompany/YetiForceCRM/issues/13856#issuecomment-738333411