#Flows토론 중인 항목 10개
- 최근 활동
- 생성 날짜
- 추천 항목
- 모든 질문
- 인정받은 답변이 있는 질문
- 미답변 질문
- 인정받은 답변이 없는 질문
I have a Flow that needs to send an email when a record is created on a Custom Object. No matter what I put in the recipient field, I continue to get "0 recipients Error ID: 1728011022-505532"when I try to trigger the flow.
What I first tried was go search resources, triggering record -> Respondent field (this looks up the contact) ->Contact ID:
When that failed, I tried several different versions of creating a text variable to look up the same thing and put that in the recipient ID field. Again, no luck. Finally, I switched the look-up from "Search Resources" to "Enter Text" and put in the text of a contact ID I know for sure is active and has a valid email address, but still got the error.
For this flow, I need to have it pull the email address of the Contact (Respondent) listed in these records. What am I missing?
#Flow #Flows #Custom Objects
답변 3개
Hi, see the tool tip on the Recipient Addresses field which says it needs to have an email address not id. Try using the hardcoded email address and test to see its working.
We are performing a migration from a legacy Salesforce Username-Password OAuth integration to an External Client App using Client Credentials. To validate migration behavior, we need the org-wide setting "Allow OAuth Username-Password Flows"
enabled in our org. Could Salesforce Support confirm whether this setting can be enabled, whether any feature flags are required, and whether there are edition-specific restrictions preventing its availability?
#OAuth 2.0 #Usernames #Password #Flows #External Application
답변 2개
Hey Ramandra,
Himanshu's answer is accurate and matches what's actually being reported. Real-world evidence backs this up: even after explicitly turning on "Allow OAuth Username-Password Flows," users are still getting a "Username-Password Flow Disabled" error, confirming the toggle alone doesn't guarantee the flow will work, Salesforce's platform-level retirement enforcement can override it regardless of your org setting.
So to your three original questions:
- The setting existing and being toggleable doesn't mean the flow will actually function, this is confirmed behavior people are hitting even now
- Whether Support can override this for validation purposes is genuinely a case-by-case Support/AE conversation, not something the community can confirm
- Not edition-specific, it's the platform-wide retirement, not a licensing tier restriction
Practical suggestion: since you're already building the Client Credentials integration, validate it independently rather than trying to get the legacy flow re-enabled for a side-by-side. Compare against logs/behavior from your old integration instead of live-running both simultaneously, that avoids being blocked by something Salesforce is actively phasing out.
Reference:
https://help.salesforce.com/s/articleView?id=xcloud.remoteaccess_oauth_username_password_flow.htm&language=en_US&type=5
I have created 1 Orchestration Flow. It is breaking for 1 one of the Activity on the Connect Portal.
If I am running the Orchestration Flow outside of the Connect Portal then it is working fine and giving me the respected output.
I am working in 3-4 sandboxes but only on 1 sandbox it is giving me the following error.
An Error Occurred with Your "Project Approval Flow" Orchestration
You’ve received this email because an error occurred while your "Project Approval Flow" orchestration was running.
View debugging information for this orchestration in Flow Builder.
Error element Submit_for_Approval5 (FlowOrchestratedStage).
An error occurred. Try again, or contact Salesforce Customer Support and provide this error ID: 53194206-372493 (1440708959)
Can anyone help me with this.
Is any permission or something is missing for the connect portal because of that it is not working.
Need to find the solution asap.
#Customer Service #Flow-Orchestration
Global Medical Equipment Sales & Service Management Company MedTech Global manufactures and sells MRI machines, CT scanners, X-Ray equipment, and medical devices to hospitals worldwide. Departments: Sales Finance Service Logistics Legal Compliance Regional Managers Global VP Installation Team Support Team Objects Standard Account Opportunity Case Task Contract Asset User Quote Product Order Order Product Content Document Email Message Approval Custom Equipment_Request__c Installation__c Compliance_Check__c Finance_Approval__c Discount_Request__c Warranty__c Risk_Assessment__c Shipment__c Audit_Log__c Training_Request__c Service_Schedule__c Business Requirement Hospital submits an order for MRI Machine. Entire process must happen automatically. Step 1 Opportunity becomes Closed Won. Flow starts. Trigger After Save Decision 1 Order Amount IF Less than 100K Auto Approve IF 100K–500K Regional Manager Approval IF Above 500K Director Approval IF Above 1 Million VP Approval Decision 2 Discount % IF <10% No approval 10–20% Sales Manager 20–30% Finance Approval Above 30% CEO Approval Decision 3 Country IF USA Assign USA Team IF Canada Assign Canada Team IF Europe Assign EU Team IF Middle East Assign ME Team Else Global Team Decision 4 Customer Type Government ↓ Compliance Check Private Hospital ↓ Skip Compliance Research Institute ↓ Legal Review Decision 5 Equipment Type MRI ↓ Installation Team A CT Scan ↓ Installation Team B X-Ray ↓ Installation Team C Ultrasound ↓ Installation Team D Decision 6 Warranty Purchased? YES Create Warranty NO Skip Decision 7 AMC Purchased? YES Create Service Schedule NO Skip Decision 8 Training Required? YES Create Training Request Assign Trainer NO Skip Decision 9 Risk Score Low ↓ Proceed Medium ↓ Manager Review High ↓ Compliance Review Critical ↓ Legal Approval Decision 10 Inventory Available? YES Reserve Inventory NO Backorder Notify Procurement Get Records Customer Products Price Book Contract Previous Orders Open Cases Inventory Warranty Assets Service Team Loop Each Product MRI Monitor Battery UPS Printer Software License Training Kit For every product Create Order Product Asset Shipment Warranty Installation Task Collection Assignment Store All Tasks All Assets All Shipments Bulk Insert Create Records Order Order Products Shipment Tasks Installation Warranty Compliance Audit Training Finance Approval Update Records Opportunity Account Contract Assets Case Order Shipment Scheduled Path After 1 Hour Notify Warehouse After 24 Hours Check Shipment 48 Hours Reminder 72 Hours Escalation 7 Days Customer Follow-up 30 Days Customer Satisfaction Survey 365 Days AMC Renewal Reminder Email Notifications Sales Rep Finance Warehouse Customer Regional Manager VP Compliance Training Team Support Installation Team Custom Notification Salesforce Bell Notification Approval Required Shipment Delayed Installation Assigned Training Scheduled Payment Pending Subflows Discount Approval Compliance Check Warranty Creation Training Shipment Audit Log Customer Notification Risk Assessment Validation Rules Cannot Close Opportunity If Primary Contact Missing Cannot Submit If Hospital License Missing Cannot Approve If Discount >40% Without CEO Cannot Ship If Payment Pending Cannot Install If Compliance Pending Duplicate Rules Prevent Duplicate Hospital Duplicate Equipment Request Duplicate Warranty Duplicate Installation Record Locking During Approval Opportunity Order Contract Become Read Only Platform Events Payment Received Shipment Completed Equipment Installed Warranty Activated Invoice Generated Subscribers ERP SAP Finance Warehouse Fault Paths If Order Creation Failed ↓ Create Audit Log ↓ Email Admin ↓ Retry Queue Security OWD Opportunity Private Role Hierarchy Sales Rep ↓ Sales Manager ↓ Regional Director ↓ VP Sharing Rules Finance Can Read Orders Warehouse Can Edit Shipment Support Read Assets Legal Read Compliance Permission Sets Finance Approval Shipment Manager Warranty Team Compliance Team Field-Level Security Hide Discount Cost Price Margin Fraud Score Salary Restriction Rules Sales Rep Only Region Records Finance Only Approved Orders Warehouse Only Pending Shipments Formula Fields Profit % Margin Warranty Remaining Delivery SLA Expected Installation Date Risk Category Approval Process Opportunity ↓ Sales Manager ↓ Finance ↓ Compliance ↓ Director ↓ VP ↓ Approved Reports Orders Pending Approval Pending Shipment Delay Installation Due Warranty Expiry Training Pending High Discount High Risk Open Compliance Dashboard Daily Orders Monthly Revenue Average Approval Time Pending Shipment Top Sales Rep Delayed Installations Risk Heat Map Integration SAP ERP Payment Gateway DocuSign ServiceNow Marketing Cloud Slack Microsoft Teams MuleSoft
#Flow #Flows #Salesforce Admin
답변 1개
Hey Rohit,
This is a massive scenario — basically a full enterprise Service/Sales Cloud implementation compressed into one post, not something buildable as a single Flow. If you're using this for practice/interview prep, here's how I'd break it into buildable phases rather than trying to tackle it as one build:
1. Core Order Flow (the actual automation)
One Record-Triggered Flow on Opportunity (After Save, Closed Won) handling Decisions 1–10 in sequence. Given the branching complexity (10 decision points), structure this as a master Flow calling Subflows for each major decision block (Discount Approval, Compliance Check, Risk Assessment, etc.) — a single flat Flow with this many branches becomes unmaintainable fast.
2. Approvals — don't build all of this in Flow
Decisions 1 and 2 (amount-based and discount-based approval tiers) map much better to native Approval Processes with multi-step approval chains than to Flow-managed approval logic. Use Flow only to Submit for Approval and react to the outcome.
3. The product loop (bulk-safe)
Loop through products → build collections for Order Product, Asset, Shipment, Warranty, Installation Task → bulk-insert each collection once, outside the loop. This is the part most likely to hit governor limits if built carelessly (DML inside the loop instead of collections).
4. Scheduled Paths
Each of your time-based followups (1hr, 24hr, 48hr, 72hr, 7-day, 30-day, 365-day) is a separate Scheduled Path off the same Flow or a dedicated time-based Flow — don't try to chain these off one one Scheduled Path.
5. Everything else is configuration, not Flow
Sharing rules, OWD, Role Hierarchy, Permission Sets, Field-Level Security, Duplicate Rules, Validation Rules — all pure declarative setup, unrelated to the Flow itself. Build these first since the Flow's record access depends on them being correct.
6. Platform Events / SAP integration
These are outbound publish points from your Create Records steps (Payment Received, Shipment Completed, etc.) — straightforward Platform Event Publish actions in Flow, but the actual SAP/ERP consumption side is outside Salesforce's scope.
Given the size, I'd start with just Decisions 1–3 (approval tier, discount tier, region assignment) as a working end-to-end Flow first, then layer in the rest incrementally. Trying to build all 10 decisions + loop + scheduled paths + subflows in one pass is where this kind of build usually falls apart.
What are you actually trying to do with this — build it out as practice, or is this a real client requirement you're scoping?
🚀 New Salesforce Feature Explained: Flow Embedded Analytics
Understanding how your Salesforce Flows behave in real time just got easier!
In my latest video on Technical Potpourri, I explore Salesforce’s new Flow Embedded Analytics feature, which brings powerful visibility directly into the Flow Canvas.
🔍 What’s covered in the video?
• Total flow runs displayed on each flow element
• Clear insights into execution paths and performance
• How this helps admins and developers debug and optimize flows faster
If you work with Salesforce Flows, this feature is a game-changer for performance analysis and troubleshooting.
🎥 Watch the full video here:
👉 https://youtu.be/FdfXfq6JTqo
@The Blog Group @* Release Readiness Trailblazers *
#Flow #Flows #Screen Flow #New Releases #Release Readiness
I am doing the Superbadge: Advanced Flow for Agentforce
: MOdule 3
Getting error "We can't find a Get Records element called Get This Contact's Orders in the Refund Request flow, or it isn't configured as specified. Make sure the filter condition is setting the CustomerAuthorizedById, not CompanyAuthorizedById."
I've checked all the elements in my flow, which are correct. The conditions are correct, sort is descending by create date, limit 5 records. I've deleted and recreated the decision element several times and still not had any luck passing this part of the training. I've debugged the flow and it works as well.
Any help please recommend. (attached screenshots)
#Agentforce #Flows