Known Session Issue

Users may encounter a 401 Unauthorized error when trying to access the Activepieces pod. This error often indicates that the session token has expired, preventing users from logging in or accessing certain features.

Solution

To resolve the 401 error, follow these steps:

  1. Clear your browser cookies and cache:

    • This can help reset any expired session tokens.

    OR

    Clear application data:

    • Open the browser’s developer tools (usually by pressing F12 or right-clicking and selecting “Inspect”).
    • Navigate to the Application tab.
    • Clear the application data to remove any stored session information.

  2. Refresh the page:

    • After clearing the data, refresh the page to initiate a new session.

  3. Log in again:

    • Use your credentials to log back into the Activepieces pod.

Additional Information

We have created a GitHub issue regarding this problem, but it has not been addressed by the developers. Users experiencing this issue should follow the steps above to mitigate the problem until a permanent fix is implemented.

Troubleshooting After Updates

If you encounter errors after an Activepieces update, such as module installation failures, missing dependencies, or flows that fail to work properly, clearing the cache folder can force a clean reinstall of dependencies.

  1. Pause the pod via More > Pause in the PikaPods dashboard.
  2. Access your pod files via SFTP. (Refer to this page for accessing pod files using SFTP.)
  3. Delete everything inside the cache folder.
  4. Resume the pod via More > Resume in the PikaPods dashboard.

This will trigger Activepieces to reinstall all dependencies and pieces from scratch, which often resolves issues caused by incomplete or corrupted installations during updates.