Add a module automation failed
Last updated: October 2, 2026
Applies to: Super Admins, Creators, and Integrators
The Add a module action is available when it's turned on for your organization. If you don't see it, contact your OnRamp team.
An Add a module action copies a module from your Library into the project each time its automation runs. If the module didn't appear, the project's log shows what stopped it. We'll go through each cause and its fix.
Why it happens
When the copy fails, the log row's Action shows Add Module, and Success shows an X. To read the reason, select View in the row's Error column, and find the message line. To find the row, see Project automation didn't run or failed.
What you see in Logs | Cause |
|---|---|
Error includes | The module chosen in the action is no longer in your Library, for example because it was deleted. |
Error includes | The project is missing its Start Date or End Date. OnRamp schedules the new module's tasks from those dates. |
Error includes | OnRamp added the module, but some of its tasks couldn't be copied. The message says how many. |
Error includes | OnRamp records who added the module: the person whose action triggered the automation, or else the project owner or the project's creator. It found none of them. |
Error includes | The action doesn't have a module OnRamp can use. |
No | OnRamp doesn't run Add a module on these triggers, because each module it adds could set off the trigger again. It skips the action without a row. The automation's other actions still run. |
If Action shows addModule instead of Add Module, something unexpected stopped the action. Contact support with the details in Still stuck?.
Fix it
If Error includes
task(s) could not be copied into, the module is already in the project, without some of its tasks. Contact support with the details in Still stuck?. Running the automation again adds a second copy of the module rather than completing this one.Open the project from Projects, and select the Automations tab.
In the list of automations, select the one with the Add a module step. Its first step is the trigger.
Make the change for your row:
is not an active library module,Module ID is required for Add Module action, orInvalid module id: Select the Add a module step. In Module, the old module may be marked (archived). Select an active Library module instead, then check Schedule offset (days) and the role assignments, which reset when the module changes. If the list is empty, create or activate a module in your Library first.needs planned start and go-live dates: Select the project's Settings tab, and select dates for both Start Date and End Date.Unable to determine user to attribute module addition: Select the project's Settings tab, and select a Project Owner.No row, on Module added or Any task completed: Add the module from an automation with a different trigger, such as Task completed or Module completed. Create Project Automations walks through the steps. Then remove the Add a module step from this automation with the step's trash icon. If it's the automation's only action, select Delete Rule instead, and confirm.
If you changed an automation, select Save.
To check the fix, repeat the event on the project. Some triggers, such as Project created, happen only once per project.
Select Logs, and then select Refresh to load the new row.
Still stuck?
Contact support with the project's name and link, the automation's trigger, the module's name (module_name in Payload), the row's Timestamp, and the full text from Error.