#Flows26 人がディスカッション中

Hello Amit, 

Yes, this can happen due to backend synchronization/caching. Newly created Flows may take a few minutes before they become available in the Reference Action dropdown for a subagent. It’s not usually an issue with the Flow itself. There doesn’t seem to be a fixed guaranteed propagation time, but in practice, waiting a few minutes and refreshing/reopening the action configuration usually makes the Flow appear. Hope this helps!

@Craig Munster

Ah, that's the missing piece — and you're right, I was wrong to steer you off your formula field. On an Opportunity Product button the native OpportunityId genuinely isn't exposed in the merge-field picker (annoying known quirk). Your Opportunity_Id__c CASESAFEID field is exactly the right workaround, so keep it — custom fields DO show up under Insert Field. Just reference that one instead of OpportunityId: 

/flow/Opportunity_Product_Screen_Flow_Clone_Opportunity_Product?recordId={!

}&retURL=/lightning/r/Opportunity/{!OpportunityLineItem.Opportunity_Id__c}/related/OpportunityLineItems/view 

That sends them back to the Products related list on the parent Opp. Sorry for the runaround getting there! 

If this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂

@Mario Santellan

your flow is basically right — the only broken piece is the GetFileName filter value. In that resource picker you're currently on 'Related Record ID', which is the record you attached the files to, not the uploaded file. Instead pick the Upload File component's 'Content Document IDs' output (Upload File > Content Document IDs) — that's the list of the uploaded files' Ids. Also change the operator from Equals to In, since that output is a collection: the condition should read Content Document ID In → Upload File > Content Document IDs. Equals against a collection is exactly why nothing matched. Your Title mapping is already right — Title lives on the ContentDocument record, which is why 'Content Document from GetFileName > Title' works in AddAttachmentName (Title = file name without the extension; add FileExtension if you need the .pdf/.docx part). On multiples: with 'Only the first record' selected you'll capture just the first file's name. If a partner uploads 2+ files and you want them all, switch GetFileName to 'All records', add a Loop over it, and in an Assignment append each 'Loop > Title' (plus a comma) into a Text variable, then map that variable into File Name. If one name is enough, first-record is perfect as-is. Give that a try — it should populate.

No, the Flow itself won't automatically restart just because Apex updates the same record — Salesforce doesn't loop back into the currently running Flow from within its own transaction. 

But watch out for this:

If that Apex update happens to match the entry criteria of a

One-line takeaway:

Same Flow instance won't re-run recursively, but a fresh Flow trigger can fire on that DML — so it's still safer to add a guard condition (like checking if the specific field actually changed) if you want to avoid unintended re-entry. 

Hi @Archana Chittoor

Yes, we can create a report to see the usage of Screen Flows.

Go to Reports -> Public Folders -> Sample Flow Report: Screen Flow.

This report shows:

• Which users are running the Screen Flows
• Number of flow executions
• Flow interview status
• Time users spend on each screen

By default, the report shows data from the last 7 days. We can change the date filter, but the maximum available data is 31 days.

If the report is not available, we can create a custom report type using Flow Interview Logs and Flow Interview Log Entries.

Thanks. 

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.