Change LC Flows report Email template to break lines
LeadConduit Sync monitor:
Howard Green is not zipcode error https://next.leadconduit.com/events/5fe96d3f74b6d206443bfb33 This was solved by temporarily disabling the Last Event Reason related to zipcode. For some reason, Last Event Reason is wrongly calculated by the integrationAdd a column "In CRM" Yes No -> Added CRL URL 👍
TrustedForm error: no need to be counted as error -> Same solution as the one for zipcode error
Last Event Reason is WRONG -> Patched to not include "continue" outcomes
LeadConduit Routing:
Check too many unknowns --> Many calculations are lacking the Form POST Event WHY, maybe because of timeouts? mmm could be
-> HELPED OUT :) DONE - ORIGINAL CAMPAIGN ID RETRY-SWEEP 🥇 https://github.com/intakedesk/py-leadconduit-leads-routing-process
Coded
Updated Repo
Put in Production
Will help Unknown Rule/Campaign rates
Verify that this data is accurate
Always compare against LeadConduit Sync Monitor
Add a new Branch to the Tree: Current CampaignThis overflows the visual and breaks the data a bit. Better to wait 👎
DUPLICATE mark in the Tree instead of Blanks 👍
Last Event Reason is WRONG -> Patched to not include "continue" outcomes
Azure Functions:
Try installing Hybrid Connections 🥇
It's okay to migrate things to Azure for as long as it doesn't take forever
LeadConduit notification: 👍
Don't count ZipCodeDon't count TrustedFormChange LC Flows report Email template to break linesLeadConduit Sync monitor:
Howard Green is not zipcode error https://next.leadconduit.com/events/5fe96d3f74b6d206443bfb33This was solved by temporarily disabling the Last Event Reason related to zipcode. For some reason, Last Event Reason is wrongly calculated by the integrationAdd a column "In CRM" Yes No-> Added CRL URL 👍TrustedForm error: no need to be counted as error-> Same solution as the one for zipcode errorLast Event Reason is WRONG-> Patched to not include "continue" outcomesLeadConduit Routing:
Check too many unknowns--> Many calculations are lacking the Form POST Event WHY, maybe because of timeouts? mmm could be -> HELPED OUT :) DONE - ORIGINAL CAMPAIGN ID RETRY-SWEEP 🥇 https://github.com/intakedesk/py-leadconduit-leads-routing-process Coded Updated Repo Put in Production Will help Unknown Rule/Campaign ratesAdd a new Branch to the Tree: Current CampaignThis overflows the visual and breaks the data a bit. Better to wait 👎DUPLICATE mark in the Tree instead of Blanks👍Last Event Reason is WRONG-> Patched to not include "continue" outcomesAzure Functions:
Try installing Hybrid Connections🥇 It's okay to migrate things to Azure for as long as it doesn't take forever