Flow Action Rest Call with firing but not in flow action executions list

[jasonkist]

Hello community, I'm hoping someone can help lead me to a source of an issue with a flow action. Everyday in the 'outbound http log', I see an api call from one of our integrations we setup with a flow action rest step. See screenshot.

What we know:

• This api call is randomly firing everyday but at times that aren't consistent.
• In the outbound http log, on the source tab, the source table says 'sys_hub_step_instance' and the source record id reference references the action we setup.
• This flow action is manually initiated by the user and fired from a portal widget when a user clicks a button.
• The flow action for this instance is not in the flow actions executions list
• All the other flow actions for this rest step are listed in the executions list.
• Effecting 1 user only
• Nothing in the system logs to indicated impersonation or errors.
• Not finding any related information in the ECC log

Any help on where else to look in the system would be appreciated.

[dbook]

Some questions. 

You say 'This flow action is manually initiated by the user and fired from a portal widget when a user clicks a button.' but also that 'This api call is randomly firing everyday but at times that aren't consistent.' 

Who is 'The user' in this scenario. My assumption here is as it's User initiated you would expect the API call to made inconsistently as it's not scheduled / systematically executed. Please do proivide further clarity. 

Contiuing on from this assumption, have you put any logging on when the portal widget button is clicked? If not, as a first step I would generate a log record when it is a clicked and see if the API calls match when the button is clicked. 

If the answer is yes, perhaps other Users are selecting the button but your configuration is somehow hardcoded to the impacted user in terms of the impact being felt. Without understand the exact function though theres' not much to go on. 

Some food for thought and I hope this helps you. 

[jasonkist]

I see where you're going and I've dug through all that. I guess my question is, from the first screen shot, the outbound http log shows the API call went out and was fired from the flow action, shouldn't the flow action be listed in flow executions/operations? It's not there. Its working fine for everything else(this screenshot shows the executions).

[jasonkist · Accepted solution]

Mystery solved. Users where following a link in a knowledge article to someone's hardcoded profile in a portal. So the logged on user is on a profile page of another user(yes this can happen). They click the button on the profile page to initiate a server script in the widget that calls the flow action. This explains why there isn't a flow execution of the userid in the outbound http log.