Re: Playbooks that use "agent" step connector not ...

snikam · 10-03-2023

Description This article describes the process of cloning existing HA nodes to different network segments without breaking clusters. Scope FortiSOAR HA Nodes. Solution Pre-requisites: All data ingestion schedules and listener-based data ingestions sh...

snikam · 12-23-2022

Description This article describes how to use the Email Notification Service (listener based ingestion) of the Exchange connector. Scope FortiSOAR Exchange Connector. Solution The Email Notification Service (Listener based ingestion) is a service whi...

snikam · 12-23-2022

Description This article describes how to solve the exchange connector error - Unsupported tzinfo type: _PytzShimTimezone(datetime.timezone.utc, 'UTC'). Scope Fortisoar Exchange Connector v4.0.0 or 4.1.0. Solution For Exchange v4.0.0:In the FortiSOAR...

snikam · 04-28-2025

Hi @Swapnil1 - This issue has been resolved, can you please check once?

snikam · 12-30-2024

Yes, it seems an issue when using the connector step with agent configuration in the child step.Thank you so much for pointing it out. We will fix it in an upcoming release.Meanwhile, as a workaround, please continue referring step output directly in...

snikam · 12-29-2024

HiVariables declared in child playbooks cannot be directly accessed in parent playbooks regardless of connector action executed on agent.There are two ways to achieve this:1. Add set variable step as last step in reference(child) playbook. 2. In the ...

User Statistics

User Activity

Technical Tip: Moving FortiSOAR HA Node Cluster to New Network

Technical Tip: Using the Exchange connector's Email Notification Service (Listener based ingestion)

Troubleshooting Tip: FortiSOAR Exchange Connector - Unsupported tzinfo type: _PytzShimTimezone(datetime.timezone.utc, 'UTC')

Re: FortiSOAR check readiness upgrade to 7.6.2 fails to complete due to missing entry