Greenplum Command Center(GPCC) reports: (0 , SA.isEqual) is not a function

Products

• VMware Tanzu Data Suite
• VMware Tanzu Greenplum
• VMware Tanzu Greenplum / Gemfire

Issue/Introduction

When trying to change the "Repeat Settings" in the "Recommendations" page of the GPCC version 7.6.x and 6.16.x an error is reported:

Unexpected Application Error!
(0 , SA.isEqual) is not a function
TypeError: (0 , SA.isEqual) is not a function
    at SettingsInFlyout.getScheduleForm (http://10.159.240.156:28080/static/assets/main.js?vers=7.6.1:154:306063)
    at SettingsInFlyout.render (http://10.159.240.156:28080/static/assets/main.js?vers=7.6.1:154:311320)
    at jj (http://10.159.240.156:28080/static/assets/vendor.lib.js?vers=7.6.1:37:77451)
    at hj (http://10.159.240.156:28080/static/assets/vendor.lib.js?vers=7.6.1:37:77250)
    at za (http://10.159.240.156:28080/static/assets/vendor.lib.js?vers=7.6.1:37:120348)
    at Uk (http://10.159.240.156:28080/static/assets/vendor.lib.js?vers=7.6.1:37:108567)
    at Tk (http://10.159.240.156:28080/static/assets/vendor.lib.js?vers=7.6.1:37:108495)
    at Ik (http://10.159.240.156:28080/static/assets/vendor.lib.js?vers=7.6.1:37:108358)
    at Nk (http://10.159.240.156:28080/static/assets/vendor.lib.js?vers=7.6.1:37:105191)
    at Ek (http://10.159.240.156:28080/static/assets/vendor.lib.js?vers=7.6.1:37:105573)

Environment

Greenplum Command Center 7.6.x

Greenplum Command Center 6.16.x

Cause

The issue is because of the bad import of "isEqual" method from lodash.

Resolution

Fix

Issue is fixed in Greenplum Command Center 6.17.0 and 7.7.0

Workaround

It is possible to change the schedule by altering the table "gpmetrics.gpcc_schedule" in the "gpperfmon" database.

Note: Do not change while a recommendation table scan is in progress.

The query below will update the schedule settings and apply new schedule.

BEGIN;

UPDATE gpmetrics.gpcc_schedule
SET etime = now()
WHERE schedule_id = 1 AND etime IS NULL;

INSERT INTO gpmetrics.gpcc_schedule (schedule_id, description, schedule_config)
VALUES (
  1,
  'GPCC scan tables for recommendation report',
  '{"start":"YYYY-MM-DD HH:MM:SS","duration":"2h","repeat":"none"}'::json
);

COMMIT; 

The possible options for the schedule_config JSON:

Field	Note
start	Date and time in the format "YYYY-MM-DD HH:MM:SS"
duration	"unlimited" or "1h", "2h",....""24h"
repeat	"none", "daily" or "weekly-<interval>-<d1>-<d2>-…"  — <interval> can be 1–12, <dX> can be 1-7 where 1=Mon … 7=Sun

Example of 2 hour duration and no repeat:

'{"start":"2026-03-23 02:00:00","duration":"2h","repeat":"none"}'::json

Example of every week on Saturday at 2 AM:

'{"start":"2026-03-21 02:00:00","duration":"unlimited","repeat":"weekly-1-6"}'::json

Verify the DB setting with:

SELECT schedule_id, schedule_config, ctime, etime
FROM gpmetrics.gpcc_schedule
WHERE schedule_id = 1
ORDER BY ctime DESC
LIMIT 5;

Verify using the WebUI:

Reload the "Recommendations" page on the UI to verify the changes.