If the connection to PlentyOneBase fails with error messages such as "No connection to PlentyONE Base established" or "Not connected (No secure connection)", this may be due to a blocked permission in the Google Chrome browser.This often occurs even though the standard error sources have already been checked.Check known standard error sourcesBefore checking the browser settings, make sure the following common causes are excluded:Port check: The port (default 7331) is correctly occupied by PlentyOneBase and is not blocked.Access Token: The Access Token in the PlentyONE backend and in the local PlentyOneBase configuration are identical.Local firewall: The Windows Defender Firewall or third-party antivirus software does not block the connection (if necessary, disable temporarily for testing).DNS rebind protection: If you use a router such as the Fritz!Box, make sure that the domain local.plentybase.de has been added as an exception.Solution: Check Chrome permission for local networkIf the above points do not solve the problem, the cau...

Usually, execution gets stuck at a filter, or the trigger is configured differently than expected. The Flow tracker shows you exactly what is causing the issue. If a Flow does not trigger, runs at the wrong time or finds the same tickets every time it runs, the following steps will help you troubleshoot the issue.Good to know: Executing userFlows run in the background without their own user. In the Flow tracker, “System” therefore always appears as the executing user for these automated actions.How to fix the issue Flow tracker and filter settings A wrongly configured filter often blocks your Flow from running. Check activation:First, check whether the Flow is active.  Important: After migrating from event actions, you must activate the Flow first and only then deactivate the old event action. Use the Flow tracker:Open the Flow tracker and navigate to the overview of filtered Flow executions. There you can see at a glance which filter stopped an execution. Optimise multiple filters:If you filter by several values (e.g. different ...

It may be that your event action (EA) is not triggered because the set trigger does not match the actual status with which new orders are imported into your system.Problem: Trigger status and order status do not matchYou may have configured an event action to respond to the event New order in order to send an order confirmation.However, if your orders are loaded into the system (e.g. via an import or a marketplace connection) with the status New incomplete order, the trigger New order does not apply, and the action is not executed.Solution: Adjust the trigger of the event actionIn order for your event action (e.g. for the order confirmation) to respond immediately after the order is received in the system, you need to change the trigger in the configuration of the respective event action.Adjust the trigger from New order to New incomplete order.