I have the following Time Offset Flag adapter transformation configured:

For the problematical entity the EndTimestampUTC field is "4/22/2021 12:00:00 PM" (i.e. midnight at the start of April 23rd in my customer's timezone - NZ), so the corresponding UTC timestamp for the threshold comparison should be "5/7/2021 12:00:00 PM" (i.e. midnight at the start of May 8th in NZ timezone).  EndTimestampUTC was changed to that value on May 7 (i.e. before UTC 5/7/2021 12:00:00 PM) but even though today is now May 10th the PostEndPlus14 field hasn't been re-evaluated to "Yes" as I would have expected (i.e. transition from the ">" case to the "<" case).

To allow a better chance to debug I have not run a Generate Changes on the adapter yet.

How soon will temporal transformations (e.g. Time Offset) be re-evaluated after the current date and time changes?

When a Baseline Sync runs on a link the connector's update export functionality is called to update every entity, even when there are no field value changes.  This places an unnecessary load on UNIFYBroker and performs null updates against the external system for no discernible reason, and since UNIFYBroker/Plus is unable to sync any other links while this takes place can result in unnecessary processing delays while the connector is busy effectively doing nothing.

When an non-enabled adapter is queried via ODATA the endpoint returns a 404 error.  A different error with some descriptive text would make it easier to work out what has gone wrong.

I am seeing: Baseline synchronization failed with the message "Source entity 'b5d56da5-a8af-4088-b98c-4b78a693b093' shares a join target with another source entity: 'fa457ecd-b5a7-4708-886b-747ca82da40a'. Cannot proceed with join.". See logs for more details.

Both source entity have a join field value of NULL, and there are no target entities with a join field value of NULL.

I tried deleting entities and reloading them, but the error remains. The mapping of field values through to other locker entities is not happening, and I would like to know if the join failure is the cause of this.

Add a feature to allow a timeout to be specified for a PowerShell connector operation (Import All, etc).  When the timeout expires, forcibly kill the PowerShell operation and log an error.

This came up because a connector hung for ten days in a UNIFYConnect environment until I noticed.  All of the other connectors in the same connector exclusion group were blocked from running as well.  I suggest a default timeout of one hour for most operations and 10 minutes for Import Changes.

Hi,

Recently we ran into an issue with the Google Apps Connector where going into update the connector properties would set the agent to another rather than keeping the original value.

This caused an issue where we saved the connector without realizing the agent had been changed, causing the connector to import from another domain.

We can make sure the agent is set correctly before we make any updates, but it would be useful to have this behavior changed to avoid any issues accidents in future. Google Connector version is 5.3.2.0

Thanks

Most UNIFYBroker agents have a Test Connection operation, but this can't be configured for PowerShell connectors.  This morning my customer's PowerShell connectors were failing because Azure was reporting the MS Graph API to be overloaded and only accepting admin connections (“53300: remaining connection slots are reserved for non-replication superuser connections”).

Add a Test Connection facility to a PowerShell connector.  This would tie in with https://voice.unifysolutions.net/en/communities/6/topics/4220-scheduled-execution-of-test-connection-on-agents

I have an environment where we are noticing some membership disparities for some google groups that are failing on export. My question around this is when a group membership fails to update for whatever reason, will the export process continue and try to amend the remaining membership changes for that group? Or will it simply throw the error back to MIM and move on to the next group in the export? UNIFYBroker and the Google Connectors are at the latest versions.

Thank you

When a locker's Cloud Group Name field is updated this configuration causes the creation of a new adapter/connector entity.  The old adapter/connector entity is retained.  After the 

The functionality is needed to allow solutions to have changes to entity key/join fields flow through to downstream systems.