Hi @Luis Andrés Jara Vásquez ,
This is actually a common scenario when using Ultimate PDF across modules, and it usually comes down to URL accessibility, dependencies, or visibility issues.

Below are some ways to check and fix..

• Is the Screen Public?
  If you're calling /XXXXXX_Request_Form_EU/ApproversFlowLimitedV3 from another module, the screen you're trying to render must be set as Public.

How to check:

1. Go to the screen in the target module
2. Select the screen in the Interface tab
3. In the Properties panel, set "Public" = Yes (True)

If it’s not public, the PDF engine can’t access it and will fail silently or return an error.

• Check if the Screen Requires Login
  If the screen you're trying to render requires authentication, and Ultimate PDF tries to render it without a valid session, it may break.

Some options are:

 – Allow Anonymous Access (for rendering only):

1. In the screen properties, temporarily set (tick) "Anonymous" = 'Yes' (☑️)
2. Or create a clone of the screen that renders the same layout, but allows "Anonymous" access and doesn’t require user session

 – Use Session Cookie (Advanced)

1. Set the SessionId input when calling the GeneratePDF server action
2. This ensures the PDF rendering engine has the same session context as the user

Security tip: Don’t expose sensitive data unless you’re handling session validation securely.

• Is the Screen Rendering Properly in Browser?
  Test the URL in a private/incognito browser window. If it doesn’t load fully there (because of login or permissions), Ultimate PDF also won’t be able to render it.

• Check Dependencies Between Modules
  If the new module doesn’t have Ultimate PDF properly referenced, or if the module structure was cloned or renamed, it can cause unexpected errors.
  Go to Manage Dependencies;
  -- Ensure UltimatePDF, UltimatePDF_Management, or any necessary components are correctly added.

Wrap your target screen with a fake layout and remove all logic to test if the rendering engine works. This helps isolate whether the issue is in the screen’s logic or in the PDF engine setup.

Hope this addresses the issue.

Thanks and Regards!