appsmithorg/appsmith · error · Error

Unable to fetch newly created actions

Error message

Unable to fetch newly created actions

What it means

Error thrown by the one-click-binding flow after the actions were created. The saga dispatches fetchActions and waits on either FETCH_ACTIONS_SUCCESS or FETCH_ACTIONS_ERROR; if the error variant wins, the just-created actions cannot be located in the refreshed store and the binding aborts.

Source

Thrown at app/client/src/sagas/OneClickBindingSaga.ts:216

      const createdActions: Action[] = yield all(
        payloadList.map((payload) =>
          call(createActionsForOneClickBindingSaga, omit(payload, "type")),
        ),
      );

      if (createdActions.some((action) => !action)) {
        throw new Error("Unable to create Actions");
      }

      yield put(fetchActions({ applicationId }, []));

      const fetchAction: ReduxAction<unknown> = yield take([
        ReduxActionTypes.FETCH_ACTIONS_SUCCESS,
        ReduxActionErrorTypes.FETCH_ACTIONS_ERROR,
      ]);

      if (fetchAction.type === ReduxActionErrorTypes.FETCH_ACTIONS_ERROR) {
        throw new Error("Unable to fetch newly created actions");
      }

      const actionsToRun = createdActions.filter(
        (action) =>
          action.name === queryNameMap[QUERY_TYPE.SELECT] ||
          action.name === queryNameMap[QUERY_TYPE.TOTAL_RECORD],
      );

      //TODO(Balaji): Need to make changes to plugin saga to execute the actions in parallel
      for (const actionToRun of actionsToRun) {
        yield put(
          runAction(
            actionToRun.id,
            undefined,
            true,
            undefined,
            ActionExecutionContext.ONE_CLICK_BINDING,
          ),

View on GitHub (pinned to 8cd9021c24)

Solutions

1. Retry the one-click binding; the created actions usually persist and the refresh succeeds on retry.
2. If it reproduces, inspect the FETCH_ACTIONS network request status and the redux error payload.
3. Verify no second session deleted the just-created actions.

When it happens

Trigger: The create calls succeeded but the subsequent list refresh failed (network drop, 5xx on the list endpoint, throttling). Less commonly, the actions were created in a different application context and the fetch returns empty.

Common situations: Flaky network immediately after creation; backend list endpoint slower than the wait window; race with another tab that deleted the actions.

Related errors

• Save page failed
• ${extractExecutionErrorMessage(e)}
• Failed to load JS libraries
• Unable to create Actions
• Unable to run action: ${actionToRun.name}

AI-assisted analysis of appsmithorg/appsmith@8cd9021c24 (2026-08-12). Data as JSON: /api/errors/9ad2d3960a328a48. Report an issue: GitHub.