Process Federation Server messages reference

Message codes starting with CWMFS

CWMFS0000I: The federated data repository monitoring service is starting

Explanation	The Process Federation Server federated data repository monitoring service, that monitors the availability of the federated data repository, is starting. This message is expected at the start of Process Federation Server.
Action	No action required

CWMFS0001I: The federated data repository monitoring service is stopping

Explanation	The Process Federation Server federated data repository monitoring service, that monitors the availability of the federated data repository, is stopping. This message is expected when Process Federation Server is stopping.
Action	No action required

CWMFS0008E: A severe error has stopped the federated data repository monitoring service: {0}. Process Federation Server must be restarted to restart the federated data repository monitoring service.

Explanation	A severe error (with message {0}) occurred in the federated data repository monitoring service, that monitors the availability of the federated data repository, causing it to stop running.
Action	In addition to the error displayed in the message, an FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause. Once the error cause is solved, the Process Federation Server instance must be restarted in order for the federated data repository monitoring service to be restarted.

CWMFS0009I: The remote federated data repository cluster is up and running: registering the federated data repository service.

Explanation	The remote federated data repository cluster is up and running and the federated data repository service, that connects Process Federation Server to the federated data repository service, is now available.
Action	No action required

CWMFS0010W: The remote federated data repository cluster is not responding: unregistering the federated data repository service.

Explanation	The remote federated data repository cluster is not responding and the federated data repository service, that connects Process Federation Server to the federated data repository service, is not available anymore.
Action	Ensure that the remote federated data repository cluster is up and running and can be reached through the endpoint URLs specified in the configuration element in server.xml.

CWMFS0011I: The remote federated data repository cluster status is now {0}

Explanation	The status of the federated data repository cluster has changed and is now one of the following: "green" (all shards are assigned), "yellow" (all primary shards are assigned but one or more replica shards are unassigned), or "red" (one or more primary shards are unassigned).
Action	If the displayed status is not "green", you must take action on the federated data repository cluster in order to bring it to a "green" state.

CWMFS0012E: An error occurred when contacting the remote federated data repository cluster: {0}

Explanation	A communication error occurred when monitoring the availability of the federated data repository cluster.
Action	use the error message {0} to diagnose and fix the cause of the communication error.

CWMFS0013E: The remote federated data repository cluster is not in green or yellow status. Process Federation Server will not work until the problem with the federated data repository is fixed.

Explanation	Process Federation Server cannot work because the remote federated data repository cluster is failing.
Action	Fix the error with the federated data repository (Opensearch/Elasticsearch) to allow Process Federation Server to run.

CWMFS0500E: Error adding index document to federated data repository

Explanation	No additional information available
Action	No action required

CWMFS1005E: Failed to create the index {0}.

Explanation	Process Federation Server failed to create an index in the federated data repository.
Action	In addition to the error displayed in the message, an FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS1006E: The indexName must be lower case, cannot begin with an underscore and cannot contain commas.

Explanation	The indexName property of an ibmPfs_federatedSystem configuration element in server.xml contains upper case characters, or begins with an underscore, or contains commas.
Action	Update the indexName property value to use lower case charaters, not begin with an underscore and not contain any comma.

CWMFS1007W: {0} is not a supported authentication mechanism for federated system {1}. Using default value {2} instead.

Explanation	The authenticationMechanism property of an ibmPfs_federatedSystem configuration element in server.xml has an unsupported value.
Action	Use a supported value for authenticationMechanism: LTPA (default) or PFS_ACCESS_TOKEN

CWMFS1008I: Requests to federated system {0} will use {1} authentication mechanism.

Explanation	Displays the value of the authenticationMechanism property of an ibmPfs_federatedSystem configuration element in server.xml
Action	No action required

CWMFS1009E: Federated system {0} misses the following mandatory property: {1}.

Explanation	A mandatory property for an ibmPfs_federatedSystem configuration element in server.xml is missing.
Action	Update the ibmPfs_federatedSystem configuration element in server.xml to add a value for the mandatory property specified in the error message.

CWMFS2504E: BPD indexer for {0}: An error has occurred: {1}

Explanation	An error occurred in a BPD indexer indexing data in federated data repository index {0}.
Action	In addition to the error displayed in the message at {1}, an FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS2505E: BPD indexer for {0}: Maximum number of failures exceeded.

Explanation	The maximum number of consecutive errors after which a BPD indexer will stop processing data, defined by attribute numberOfRetries of the ibmPfs_bpdIndexer configuration element in server.xml has been reached.
Action	The PFS server must be restarted in order to restart the indexer. If BPD indexers shouldn't be stopped whatever the number of consecutive errors occurring during the indexing, attribute numberOfRetries of the ibmPfs_bpdIndex configuration element in server.xml should be set to value -1.

CWMFS2507I: BPD indexer for {0}: Synchronized {1,choice,0#0 tasks|1#1 task|1<{1} tasks} in {2,choice,0#less than one second|1#1 second|1<{2} seconds}.

Explanation	A SyncTasks maintenance operation completed for a BPD indexer indexing data in federated data repository index {0}. The message details how many tasks where synchronized and how long it took.
Action	No action required

CWMFS2508E: BPD indexer for {0}: Unable to register as a change log consumer. The indexer cannot continue.

Explanation	All the consumer columns defined in the PFS_CHANGE_LOG_CONSUMER table have been claimed.
Action	Ensure that all the CONSUMER_* columns defined in the PFS_BPD_CHANGE_LOG table have a corresponding row in the PFS_CHANGE_LOG_CONSUMER table.

CWMFS2509W: Task for taskId={0} was not found in Business Automation Workflow and will be deleted from the search index.

Explanation	A BPD indexer found a task that has been deleted from the federated BPD database and will delete it from the search index.
Action	No action required

CWMFS2510W: Indexing operation exceeded the operations warning threshold of {0} milliseconds: {1}ms

Explanation

A BPD indexer cycle took more that the threshold defined by attribute indexProcessingWarningThreshold of the ibmPfs_bpdIndexer configuration element in server.xml (default value: 3 seconds).

Action

If this warning is displayed for each cycle, it indicates that the indexing performances do not match the one specified with the threshold value. Low indexing performances can be caused by a slow connection to the federated database, a performance issue on the federated database, of performance issue with the federated data repository. Setting the trace level to com.ibm.bpm.federated.indexer.bpd.*=all will generate indexer traces that can help to diagnose the performance issue.

CWMFS2511W: Maintenance Operation {0} exceeded the operations warning threshold of {1} milliseconds: {2}ms

Explanation	A maintenance operation of a BPD indexer took more that the threshold defined by attribute maintenanceProcessingWarningThreshold of the ibmPfs_bpdIndexer configuration element in server.xml (default value: 5 seconds).
Action	If this warning is displayed everytime a maintenance operation is run, that may indicate a performance issue with the federated BPD database or that the maintenance operation should be run more often.

CWMFS2512I: Activating BPD Indexer {0} for federated system {1}.

Explanation	The BPD indexer with identifier {0}, defined in server.xml for federated system {1}, has been activated.
Action	This message is expected at the start of the PFS server for each BPD indexer defined in server.xml. If this message is not displayed in the logs, that means that the corresponding indexer has not been activated and will not run.

CWMFS2513W: Deactivating BPD Indexer {0} for federated system {1}.

Explanation	The BPD indexer with identifier {0}, defined in server.xml for federated system {1}, has been deactivated and will stop indexing data.
Action	This message is expected for each BPD indexer defined in server.xml when the PFS server stops. If this message is displayed while the server is not stopping, it indicates that a dependency of the indexer component (such as the federated data repository) is not available anymore.

CWMFS2514E: BPD indexer for {0}: The attribute {1} must be specified in the format {2}.

Explanation	The timestamp attribute {1} defined in an ibmPfs_bpdIndexer configuration element in server.xml is not in the expected format.
Action	Specify a value for this timestamp attribute that match the specified format {2}

CWMFS2515E: BPD indexer for {0}: The attribute {1} cannot be newer than current time : {2}

Explanation	The timestamp attribute {1} defined in an ibmPfs_bpdIndexer configuration element in server.xml has a value that is not in the past.
Action	Specify a value that is in the past for this timestamp attribute

CWMFS2516E: Failed to register MBean {0}.

Explanation	Process Federation Server failed to register an MBean for a BPD indexer.
Action	An FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS2517E: Failed to unregister MBean {0}.

Explanation	Process Federation Server failed to unregister the MBean of a BPD indexer.
Action	An FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS2518W: Process Instance for instanceId={0} was not found in Business Automation Workflow and will be deleted from the search index.

Explanation	A BPD indexer found a process instance that has been deleted from the federated BPD database and will delete it from the search index.
Action	No action required

CWMFS2519I: BPD indexer for {0}: Synchronized {1,choice,0#0 instances|1#1 instance|1<{1} instances} in {2,choice,0#less than one second|1#1 second|1<{2} seconds}.

Explanation	A SyncInstances maintenance operation completed for a BPD indexer indexing data in federated data repository index {0}. The message details how many process instances where synchronized and how long it took.
Action	No action required

CWMFS2520W: Ignoring request for unscheduled execution of operation {0} because instance indexing is not enabled for federated system {1}.

Explanation	A request to run an unscheduled execution of maintenance operation {0} has been ignored by Process Federation Server because instance indexing is not enabled for federated system {1}, which means that running this maintenance operation is useless.
Action	No action required

CWMFS2530E: Invalid state: BPD Indexer Daemon does not exist.

Explanation	An operation was triggered on a BPD indexer (for example, a request to backup the indexer state) while the state of the indexer does not allow it (the indexer is in an initializing state and is not yet able to perform the requested operation).
Action	Wait for the indexer initialization to have completed (log messages signaling that the indexer has started indexing) before re triggering the requested operation.

CWMFS2531E: No argument is provided.

Explanation	No additional information available
Action	No action required

CWMFS2532E: Process Instance ID is required and must be a positive Long value.

Explanation	No additional information available
Action	No action required

CWMFS2533E: Task ID must be a positive Long value.

Explanation	No additional information available
Action	No action required

CWMFS2534W: No process instance document to update as process instances are not indexed.

Explanation	No additional information available
Action	No action required

CWMFS2535E: No Search Data Persistence Manager.

Explanation	No additional information available
Action	No action required

CWMFS2536E: The process instance id {0} provided as argument is wrong because the task {1} belongs to process instance {2}.

Explanation	No additional information available
Action	No action required

CWMFS2537W: BPD indexer for {0}: federated data repository reported {1} indexing failure(s) with message "{2}". The indexer will retry during the next indexing cycle.

Explanation	Indexing failure(s) have been reported by the federated data repository when a BPD indexer tried to update documents in index {0}.
Action	Use the indexing failure messages reported in this log to diagnose and fix the issue in the federated data repository.

CWMFS2538E: Agent {0} for {1}: An error occured when trying to retrieve a restoration timestamp from index {2} ({3})

Explanation	A restoration of a BPD indexer state was requested but an error occurred when Process Federation Server tried to retrieve the restoration timestamp from the index.
Action	Use the error message provided in the log to diagnose and fix the issue.

CWMFS2539W: Agent {0} for {1}: rebuild of index {2} has been requested but no restoration timestamp can be found in the index: canceling the request.

Explanation	A restoration of a BPD indexer state was requested but no restoration timestamp was retrieved from the index, so the request has been cancelled.
Action	Make sure to perform backups before requesting a restoration.

CWMFS2540I: Agent {0} for {1}: rebuild of index {2} has been requested and partial re-indexing of events from {3} will be performed.

Explanation	A restoration of a BPD indexer state was requested and is now starting.
Action	No action required

CWMFS2541I: Agent {0} for {1}: reset of all consumer column {2} entries after {3} has been completed.

Explanation	The restoration of a BPD indexer state has completed.
Action	No action required

CWMFS2542I: Agent {0} for {1}: re-indexing of events has been requested for index {2}. This will be performed on the next indexers restart.

Explanation	A request to restore a BPD indexer state has been recorded. The restoration will be performed on the next indexer restart.
Action	Restart a PFS server to trigger a restart of the BPD indexers.

CWMFS2543I: Agent {0} for {1}: re-indexing of events has been canceled for index {2}.

Explanation	A previous request to restore a BPD indexer state has been cancelled.
Action	A new request to restore the BPD indexer state will need to be issued in order to trigger a restoration when the indexer restart.

CWMFS2544I: Agent {0} for {1}: backup of the current indexer state has been performed in index {2} with restoration timestamp {3}.

Explanation	A backup of the current state of a BPD indexer has successfully completed.
Action	A snapshot of the index can now be completed in order to backup it.

CWMFS2545W: Agent {0} for {1}: last indexer state backup has been deleted from index {2}. It is now impossible to perform a restoration.

Explanation	The last state backup of BPD indexer has been deleted.
Action	Request a new backup of the BPD indexer state when a backup is needed.

CWMFS2546I: Agent {0} for {1}: Initialization completed.

Explanation	The initialization of the BPD indexer has completed and it will now start to index data in the federated data repository.
Action	No action required

CWMFS2547W: BPD indexer for {0}: error with message "{2}" when trying to index / update / delete {1} documents in the federated data repository. The indexer will retry during the next indexing cycle.

Explanation	An error occured when a BPD indexer tried to index data in the federated data repository.
Action	Use the error message provided in the log to diagnose and fix the issue.

CWMFS3007E: An error has occurred with BPEL Indexer: {0}, caused by {1}.

Explanation	An error occurred in a BPEL indexer indexing data in federated data repository for federated system {0}.
Action	In addition to the error displayed in the message at {1}, an FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS3008E: The BPEL Indexer {0} has exceeded the maximum number of failures.

Explanation	The maximum number of consecutive errors after which a BPEL indexer will stop processing data, defined by attribute numberOfRetries of the ibmPfs_bpelIndexer configuration element in server.xml has been reached.
Action	The PFS server must be restarted in order to restart the indexer. If BPEL indexers shouldn't be stopped whatever the number of consecutive errors occurring during the indexing, attribute numberOfRetries of the ibmPfs_bpelIndex configuration element in server.xml should be set to value -1.

CWMFS3201E: Error occurred during retrieval of process instance {0} data, exception is {1}.

Explanation	An error occurred when a BPEL indexer tried to retrieve data of process instance {0} from the federated BPEL database.
Action	In addition to the error displayed in the message at {1}, an FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS3202E: Error occurred during retrieval of process template {0} data, exception is {1}.

Explanation	An error occurred when a BPEL indexer tried to retrieve data of process template {0} from the federated BPEL database.
Action	In addition to the error displayed in the message at {1}, an FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS3203E: Error occurred during retrieval of data for object {0}, exception is {1}.

Explanation	An error occurred when a BPEL indexer tried to retrieve data of object {0} from the federated BPEL database.
Action	In addition to the error displayed in the message at {1}, an FFDC file with a complete stack trace of the error may have been generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS3205E: Null pointer exception {0} occurred during retrieving task instance {1} information.

Explanation	A NullPointerException error occurred when a BPEL indexer tried to retrieve data of task instance {1} from the federated BPEL database.
Action	In addition to the error displayed in the message at {1}, an FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS3206E: Exception {0} occurred during retrieving task instance {1} information.

Explanation	An error occurred when a BPEL indexer tried to retrieve data of task instance {1} from the federated BPEL database.
Action	In addition to the error displayed in the message at {0}, an FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS3207E: Exception {0} occurred during retrieving task template {1} information.

Explanation	An error occurred when a BPEL indexer tried to retrieve data of task template {1} from the federated BPEL database.
Action	In addition to the error displayed in the message at {0}, an FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS3208E: Can not get JDBC connection from data source {0}, exception is {1}.

Explanation	An error occurred when a BPEL indexer tried to create a JDBC connection to the federated BPEL database.
Action	Use the exception details in {1} to diagnose and fix the issue.

CWMFS3210W: Sub task {0} can not be indexed because no template data could be retrieved for it.

Explanation	A BPEL indexer was not able to retrieve the template data for a task and is therefore unable to index it.
Action	No action required

CWMFS3314E: Error occurred during modify BPEL Indexer attributes: exception is {0}, caused by {1}.

Explanation	An error occurred when updating the properties of a BPEL indexer using the configuration attributes specified in server.xml
Action	Use the exception details in {0} and {1} to diagnose and fix the issue.

CWMFS3315W: The task {0} will be indexed without any process instance data.

Explanation	No BPEL process instance data could be retrieved by a BPEL indexer for a task: the task will be indexed without any business data.
Action	No action required

CWMFS3316I: Activating BPEL Indexer {0} for federated system {1}.

Explanation	The BPEL indexer with identifier {0}, defined in server.xml for federated system {1}, has been activated.
Action	This message is expected at the start of the PFS server for each BPEL indexer defined in server.xml. If this message is not displayed in the logs, that means that the corresponding indexer has not been activated and will not run.

CWMFS3317W: Deactivating BPEL Indexer {0} for federated system {1}.

Explanation	The BPEL indexer with identifier {0}, defined in server.xml for federated system {1}, has been deactivated and will stop indexing data.
Action	This message is expected for each BPEL indexer defined in server.xml when the PFS server stops. If this message is displayed while the server is not stopping, it indicates that a dependency of the indexer component (such as the federated data repository) is not available anymore.

CWMFS3318E: BPEL indexer for {0}: The attribute {1} must be specified in the format {2} : {3}.

Explanation	The timestamp attribute {1} defined in an ibmPfs_bpelIndexer configuration element in server.xml is not in the expected format.
Action	Specify a value for this timestamp attribute that match the specified format {2}

CWMFS3320E: Failed to register MBean {0}.

Explanation	Process Federation Server failed to register an MBean for a BPEL indexer.
Action	An FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS3321E: Failed to unregister MBean {0}.

Explanation	Process Federation Server failed to unregister the MBean of a BPEL indexer.
Action	An FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS3322E: Updating BPEL documents is not supported using REST API.

Explanation	No additional information available
Action	No action required

CWMFS3323W: BPEL indexer for {0}: federated data repository reported {1} indexing failure(s) with message "{2}". The indexer will retry during the next indexing cycle.

Explanation	Indexing failure(s) have been reported by the federated data repository when a BPEL indexer tried to update documents in index {0}.
Action	Use the indexing failure messages reported in this log to diagnose and fix the issue in the federated data repository.

CWMFS3324E: Agent {0} for {1}: An error occured when trying to retrieve a restoration timestamp from index {2} ({3})

Explanation	A restoration of a BPEL indexer state was requested but an error occurred when Process Federation Server tried to retrieve the restoration timestamp from the index.
Action	Use the error message provided in the log to diagnose and fix the issue.

CWMFS3325I: Agent {0} for {1}: rebuild of index {2} has been requested and partial re-indexing of events from {3} will be performed.

Explanation	A restoration of a BPEL indexer state was requested and is now starting.
Action	No action required

CWMFS3326I: Agent {0} for {1}: reset of all consumer column {2} entries after {3} has been completed.

Explanation	The restoration of a BPEL indexer state has completed.
Action	No action required

CWMFS3327W: Agent {0} for {1}: rebuild of index {2} has been requested but no restoration timestamp can be found in the index: canceling the request.

Explanation	A restoration of a BPEL indexer state was requested but no restoration timestamp was retrieved from the index, so the request has been cancelled.
Action	Make sure to perform backups before requesting a restoration.

CWMFS3328I: Agent {0} for {1}: re-indexing of events has been canceled for index {2}.

Explanation	A previous request to restore a BPEL indexer state has been cancelled.
Action	A new request to restore the BPEL indexer state will need to be issued in order to trigger a restoration when the indexer restart.

CWMFS3329E: Invalid state: BPEL Indexer Daemon does not exist.

Explanation	An operation was triggered on a BPEL indexer (for example, a request to backup the indexer state) while the state of the indexer does not allow it (the indexer is in an initializing state and is not yet able to perform the requested operation).
Action	Wait for the indexer initialization to have completed (log messages signaling that the indexer has started indexing) before re triggering the requested operation.

CWMFS3330I: Agent {0} for {1}: backup of the current indexer state has been performed in index {2} with restoration timestamp {3}.

Explanation	A backup of the current state of a BPEL indexer has successfully completed.
Action	A snapshot of the index can now be completed in order to backup it.

CWMFS3331W: Agent {0} for {1}: last indexer state backup has been deleted from index {2}. It is now impossible to perform a restoration.

Explanation	The last state backup of BPEL indexer has been deleted.
Action	Request a new backup of the BPEL indexer state when a backup is needed.

CWMFS3332I: Agent {0} for {1}: re-indexing of events has been requested for index {2}. This will be performed on the next indexers restart.

Explanation	A request to restore a BPEL indexer state has been recorded. The restoration will be performed on the next indexer restart.
Action	Restart a PFS server to trigger a restart of the BPEL indexers.

CWMFS3333I: Agent {0} for {1}: Initialization completed.

Explanation	The initialization of the BPEL indexer has completed and it will now start to index data in the federated data repository.
Action	No action required

CWMFS3334W: BPEL indexer for {0}: error with message "{2}" when trying to index / update / delete {1} documents in the federated data repository. The indexer will retry during the next indexing cycle.

Explanation	An error occured when a BPD indexer tried to index data in the federated data repository.
Action	Use the error message provided in the log to diagnose and fix the issue.

CWMFS4002E: The system ID is unknown: {0}

Explanation	A REST API has been called with a value for the system ID parameter that was not found for any federated system.
Action	Contact your system administrator for the ID value or check the federatedResults section of the query results for the 'systemID' attribute.

CWMFS4003E: The value of the ''interactionFilter'' parameter is not valid: {0}

Explanation	No additional information is available.
Action	Use one of the following values: WORK_ON, WORK_ON_ACTIVE, ASSESS_AVAILABLE, ASSESS_AND_WORK_ON, CHECK_COMPLETED, BROWSE_ALL.

CWMFS4004E: The value of the ''size'' {0} or ''offset'' {1} parameters is not valid

Explanation	The value of the size or offset parameters is not valid.
Action	Verify that the value of the parameters is zero or greater.

CWMFS4005E: The value of the ''size'' parameter ({0}) is not valid: it should be 0 or more, and less than {1} when added to the offset

Explanation	The value of the size parameter is not valid.
Action	Verify that the value of the parameter is less than the maximum value setup by the administrator.

CWMFS4007E: The {0} query cannot be executed.

Explanation	No additional information is available.
Action	Check the system logs for issues with the query execution.

CWMFS4009E: The Origin header in the REST request has more than one address.

Explanation	The Origin header in the REST request can have only one address.
Action	Submit a REST request with an Origin header that has only one address.

CWMFS4011E: Group authorization retrieval failed to complete: {0}

Explanation	The request to retrieve group information for the current user failed.
Action	Check system logs for issues with the retrieval.

CWMFS4012E: The {1} federated system does not have an index.

Explanation	No additional information is available.
Action	Check the system logs for indexing issues.

CWMFS4013E: No federated systems are currently available.

Explanation	The Process Federation Server server.xml file must have a least one configured federated system.
Action	Verify the Process Federation Server server.xml file contains a configured ibmPfs_federatedSystem element for each of the federated systems.

CWMFS4014E: None of the federated systems required to process the request are available and have an index.

Explanation	No additional information is available.
Action	Check the system logs for more details.

CWMFS4015E: The federated query service reported the following error: {0}

Explanation	No additional information is available.
Action	Check the system logs for issues with the query service.

CWMFS4016W: Ignoring the returnLastStartedDateTime query parameter because no index exist to return any last started date time.

Explanation	No additional information is available.
Action	Check the system logs for issues about missing indexes.

CWMFS4017E: The federated query service reported the following indexing failure: {0}

Explanation	No additional information is available.
Action	Check the system logs for issues with the query service indexing.

CWMFS4018E: The Origin header in the REST request does not contain an address that is an allowed origin for any federated system.

Explanation	No additional information is available.
Action	Verify that the ibmPfs_federatedSystem element in the Process Federation Server server.xml file has a configured allowedOrigins attribute.

CWMFS4019E: The request cannot be processed because the incoming REST request does not contain headers or response information.

Explanation	No additional information is available.
Action	Check the system logs for issues with the REST service.

CWMFS4020E: Internal system error : {0}

Explanation	No additional information is available.
Action	Check the system logs for issues with the REST service.

CWMFS4021E: There is no federated system declared in Process Federation Server configuration.

Explanation	No additional information is available.
Action	You must configure at least a federated system

CWMFS4023E: The value of the ''offset'': {0} task query parameter is not a valid number.

Explanation	No additional information is available.
Action	Verify that the value of the 'offset' query parameter is zero or greater.

CWMFS4024E: The value of the ''size'': {0} task query parameter is not a valid number.

Explanation	No additional information is available.
Action	Verify that the value of the 'size' query parameter is zero or greater.

CWMFS4025E: No active indexes support the sort fields: {0}

Explanation	No additional information is available.
Action	Remove the specified sort fields from the request.

CWMFS4027E: User {0} is not authorized on any of the federated systems.

Explanation	The specified user does not have access to any federated systems.
Action	Check the requesting user has access to all necessary federated systems.

CWMFS4028E: The internal REST URL prefix for the federated system is not valid: {0}

Explanation	No additional information is available.
Action	Verify that the federated system retriever in the Process Federation Server server.xml file has a value for the internalRestUrlPrefix attribute.

CWMFS4029E: The request to retrieve federated system information failed: {0}

Explanation	A request from the REST service to a federated system failed.
Action	Check the system logs for issues with the REST service request to the federated system.

CWMFS4030E: The user is not authorized for the federated system: {0}

Explanation	No additional information is available.
Action	Check that the user has access to all the necessary federated systems.

CWMFS4031E: The user security information is missing in the incoming request.

Explanation	No additional information is available.
Action	Check security authorization is enabled on the REST service.

CWMFS4032E: The request to retrieve exposed services from the {0} federated system failed.

Explanation	No additional information is available.
Action	Check the system logs for issues with REST service requests to the federated system.

CWMFS4033E: The {0} retrieval agent was not found for the federated system.

Explanation	The retrieval agent was not found for this federated system.
Action	Verify Process Federation Server has a retriever defined in the server.xml file for each federated system.

CWMFS4034E: Unable to contact the federated system: {0}

Explanation	The federated system did not respond to the request for information or status.
Action	Verify the federated system configuration in the server.xml file.

CWMFS4035W: Federated system {1} and federated system {2} have returned the same systemID {0}.

Explanation	A federated system has a unique system ID. Process Federated Server accesses the federated system and requests the system ID. When two federated systems have the same system ID, it means that the two definitions point to the same system.
Action	Verify the addresses of the federated system definitions in the server.xml file.

CWMFS4036E: The authorization has timed out for user: {1} on federated system: {0}. Check that the system clocks are synchronized across Process Federation Server and the federated system.

Explanation	There may be a difference in system clocks between Process Federated Server and the federated system causing the SSO token to be invalid on the Federated system and not on the Process Federated Server.
Action	Check the system clocks for this Process Federated Server and the federated system.

CWMFS4037W: The {1} sort field is not valid for the {0} index and was removed from the sort list.

Explanation	No additional information is available.
Action	No action required.

CWMFS4039W: The {0} index will be removed from the query because it does not support the {1} sort field.

Explanation	There is a user required sort field that does not exist on this index. Indexes cannot be sorted on non-existent fields.
Action	If the index is required, remove the sort field from the request.

CWMFS4040E: The REST service cannot access the {0} federated system. Status code: {1}

Explanation	No additional information is available.
Action	Check the system logs for issues with REST service requests to the federated system.

CWMFS4041E: The selected field is unknown: {0}

Explanation	No additional information is available.
Action	Verify the field name is a predefined field name or a business data field name.

CWMFS4042E: The {0} field is not in the list of fields defined in the current saved search.

Explanation	The field name that was requested is not allowed to be returned. Only fields that are listed in the saved search are allowed.
Action	Verify the field name exists in the saved search.

CWMFS4043E: The {0} sort field is not in the list of fields defined in the current saved search.

Explanation	The field name that was requested is not allowed to be used for sorting. Only fields that are listed in the saved search are allowed.
Action	Verify the sort field name exists in the saved search.

CWMFS4045E: The indexes on the federated system do not contain any data.

Explanation	No additional information is available.
Action	Verify that the federated systems have indexing enabled and the systems are running.

CWMFS4046E: The {0} sort field is unknown.

Explanation	No additional information is available.
Action	Verify the field name.

CWMFS4047E: The {0} sort parameter is not valid.

Explanation	The value of the sort parameter must be a comma-separated list of fields. It can include a sort order, either 'ASC' or 'DESC', for example: 'DUE ASC, PRIORITY'.
Action	Verify the sort parameter.

CWMFS4048E: The {0} sort order is not valid.

Explanation	The sort order must be one of 'ASC', 'DESC', or not used, for example: 'DUE ASC, PRIORITY'.
Action	Verify the sort order.

CWMFS4049E: The value of the ''{0}'' query parameter is not a valid date formated as YYYY-MM-DDThh:mm:ssZ (example: 2011-08-04T03:12:53Z).

Explanation	No additional information is available.
Action	Verify that the value of the query parameter is a valid date formated as YYYY-MM-DDThh:mm:ssZ (example: 2011-08-04T03:12:53Z).

CWMFS4050E: The value of the ''searchFilterScope'' query parameter is not a valid value. Valid values are: AppShortName, InstanceName, All.

Explanation	No additional information is available.
Action	Verify that the value of the 'searchFilterScope' query parameter is one of the following: AppShortName, InstanceName, All.

CWMFS4051E: The value of the ''statusFilter'' query parameter is not a valid value when restricting the search to BPD process instances. Valid values are: Active, Completed, Failed, Terminated, Did_not_Start, Suspended.

Explanation	No additional information is available.
Action	Verify that the value of the 'statusFilter' query parameter is one of the following: Active, Completed, Failed, Terminated, Did_not_Start, Suspended.

CWMFS4052E: No federated systems with process instance indexing enabled are currently available.

Explanation	The Process Federation Server server.xml file must have a least one configured federated system which performs process instance indexing.
Action	Verify the Process Federation Server server.xml file contains either a configured ibmPfs_federatedSystem element with indexProcessInstances attribute set to "true" for a BPD system or a ibmPfs_federatedSystem element for a Case Manager system.

CWMFS4053E: The system ID {0} does not match a federated system with process instance indexing enabled

Explanation	The value of the system ID parameter does not match a federated system with process instance indexing enabled.
Action	Contact your system administrator for the ID value or check the federatedResults section of the query results for the 'systemID' attribute.

CWMFS4054E: The value of the ''processTypeFilter'' query parameter is not a valid value. Valid values are: Workflow, Workstream.

Explanation	No additional information is available.
Action	Verify that the value of the 'processTypeFilter' query parameter is one of the following: Workflow, Workstream.

CWMFS4055E: The user {0} is not a manager of team {1}.

Explanation	No additional information is available.
Action	Make sure that the team exists and that the user is a manager of this team.

CWMFS4056E: The user {0} is not a manager of any team.

Explanation	No additional information is available.
Action	Make sure that the user is a manager of at least one team.

CWMFS4057E: The value of the ''units'' query parameter is not a valid value. Valid values are: DAY, HOUR.

Explanation	No additional information is available.
Action	Verify that the value of the 'units' query parameter is one of the following: DAY, HOUR.

CWMFS4058E: The value of the ''numPeriods'' query parameter is not a valid value. Valid values are integer numbers between 1 and 365.

Explanation	No additional information is available.
Action	Verify that the value of the 'numPeriods' query parameter is one of the following: DAY, HOUR.

CWMFS4059E: The value of the ''caseScope'' query parameter is not a valid value. Valid values are: Allowed, Assigned.

Explanation	No additional information is available.
Action	Verify that the value of the 'caseScope' query parameter is one of the following: Allowed, Assigned.

CWMFS4060E: The value of the ''searchFilterScope'' query parameter is not a valid value. Valid values are: AppShortName, InstanceName, TemplateId, All.

Explanation	No additional information is available.
Action	Verify that the value of the 'searchFilterScope' query parameter is one of the following: AppShortName, InstanceName, TemplateId, All.

CWMFS4061E: The value of the ''statusFilter'' query parameter is not a valid value. Valid values are: Active, Completed, Failed, Terminated, Did_not_Start, Suspended, New, Initializing, Working.

Explanation	No additional information is available.
Action	Verify that the value of the 'statusFilter' query parameter is one of the following: Active, Completed, Failed, Terminated, Did_not_Start, Suspended, New, Initializing, Working.

CWMFS4062E: The value of the ''statusFilter'' query parameter is not a valid value when restricting the search to Case instances. Valid values are: New, Initializing, Working, Completed, Failed.

Explanation	No additional information is available.
Action	Verify that the value of the 'statusFilter' query parameter is one of the following: New, Initializing, Working, Completed, Failed.

CWMFS4063E: The value of the ''instanceType'' query parameter is not a valid value. Valid values are: BPD, Case, All.

Explanation	No additional information is available.
Action	Verify that the value of the 'instanceType' query parameter is one of the following: BPD, Case, All.

CWMFS4064E: Cannot find team member {0} for team {1}.

Explanation	No additional information is available.
Action	Make sure that the team exists, that the user is a manager of this team and that the team member also exists.

CWMFS4065E: The user {0} has not access to any process with exposed performance metrics.

Explanation	No additional information is available.
Action	Make sure that the user has access to at least one process with exposed performance metrics.

CWMFS4066W: Too much processes to get summary information about ({0}), processing the first {1} entries.

Explanation	The maximum number of processes that can be processed by the process summary API is limited by the lowest index.max_terms elasticsearch or opensearch setting of the federated systems indices.
Action	Make sure that the elasticsearch or opensearch index setting index.max_terms is at least equal to the number of processes to get summary information about.

CWMFS4067E: The user {0} has not access to the performance metrics of process {1}.

Explanation	No additional information is available.
Action	Make sure that the user has access to the performance metrics of the process.

CWMFS4068E: The value of the ''riskState'' parameter is not valid: {0}. Valid values are Overdue, AtRisk, OnTrack.

Explanation	No additional information is available.
Action	Use one of the following values: Overdue, AtRisk, OnTrack.

CWMFS4069E: The value of the ''sortCriteria'' parameter is not valid: {0}. Valid values are AGE, RISK, DUEDATE, ALPHABET.

Explanation	No additional information is available.
Action	Use one of the following values: AGE, RISK, DUEDATE, ALPHABET.

CWMFS4070E: The value of the ''sortOrder'' parameter is not valid: {0}. Valid values are ASC, DESC.

Explanation	No additional information is available.
Action	Use one of the following values: ASC, DESC.

CWMFS4072W: The request to retrieve business data with origins from federated system {0} failed with HTTP error {1}.

Explanation	No additional information is available.
Action	Check that the federated system REST API can be called by the user.

CWMFS4073E: The value provided for the ''{0}'' query parameter, "{1}", is not a valid time zone provided as a IANA time zone id (example: America/Los_Angeles) or as a GMT offset between GMT-18:00 and GMT+18:00 included (example: GMT+01:00).

Explanation	No additional information is available.
Action	Verify that the value of the query parameter is a valid time zone provided as a IANA time zone id (example: America/Los_Angeles) or as a GMT offset between GMT-18:00 and GMT+18:00 included (example: GMT+01:00).

CWMFS4100E: The query filter {0} field is not in the list of fields defined in the current saved search. Only the following fields can be used in the query filter: {1}

Explanation	No additional information is available.
Action	Verify the field name.

CWMFS4101E: The query filter {0} operator is not known.

Explanation	No additional information is available.
Action	Verify the operator.

CWMFS4102E: The query filter {1} operator is not valid for the query filter {0} field. The list of valid operators for this field is: {2}

Explanation	No additional information is available.
Action	Verify the operator and field.

CWMFS4103E: The query filter {0} field with the {1} operator allows only one value.

Explanation	No additional information is available.
Action	Verify the operator and the values.

CWMFS4104E: The value {0} is not valid with the query filter operator {1} for field {2}

Explanation	No additional information is available.
Action	Verify the field and the value.

CWMFS4105E: The query filter does not have value for the condition.

Explanation	No additional information is available.
Action	Verify the value.

CWMFS4106E: The value of the query filter condition has an unknown type: {0}

Explanation	No additional information is available.
Action	Verify the value.

CWMFS4109E: The {0} query filter is not properly formed and cannot be parsed.

Explanation	No additional information is available.
Action	Verify the query filter.

CWMFS4110E: The fuzzy search ''~'' symbol must be at the end of a word: {0}

Explanation	No additional information is available.
Action	Verify the contents of all search words and place the fuzzy '~' symbol only at the end of a word.

CWMFS4111E: Phrase search not allowed on all federated systems.

Explanation	The federated index was built without word positioning information. Current field mappings on new index will include position information.
Action	Rebuild the federated system index.

CWMFS4112E: An unknown error occured when processing the query filter.

Explanation	An unknown error occured when processing the query filter.
Action	Report the error to your administrator.

CWMFS4113E: The value of the ''size'' parameter ({0}) is not valid: it should be 0 or more, and less than {1}

Explanation	The value of the size parameter is not valid.
Action	Verify that the value of the parameter is less than the maximum value setup by the administrator.

CWMFS4114E: The value of the ''size'' parameter ({0}) is not valid: it should be more than 0.

Explanation	The value of the size parameter is not valid.
Action	Verify that the value of the parameter is more than zero.

CWMFS4120E: The {0} saved search is not properly formed and it cannot be parsed.

Explanation	No additional information is available.
Action	Verify the saved search definition.

CWMFS4121E: Invalid search meta data type: {0}

Explanation	No additional information is available.
Action	Verify that the meta type exists.

CWMFS4122E: The saved search was not found: {0}

Explanation	No additional information is available.
Action	Verify the name or ID of the saved search.

CWMFS4124E: A saved search with this name already exists: {0}

Explanation	No additional information is available.
Action	Use a different name for the saved search.

CWMFS4125E: The {0} organization value for the saved search is not valid.

Explanation	No additional information is available.
Action	Valid organization values are 'byTask' and 'byProcess'.

CWMFS4126E: The {0} sort order in the saved search is not valid.

Explanation	No additional information is available.
Action	Valid sort order values are 'ASC' and 'DESC'

CWMFS4127E: The {0} condition operator in the saved search is not valid.

Explanation	No additional information is available.
Action	Valid operators are 'Equals', 'NotEquals', 'StartsWith', 'Contains', 'LessThan', 'GreaterThan', and 'FullTextSearch'

CWMFS4128E: The {0} field name in the saved search is not valid.

Explanation	No additional information is available.
Action	Verify the field name.

CWMFS4129E: The {0} constraint field name in the saved search is not valid.

Explanation	No additional information is available.
Action	Verify the field name.

CWMFS4130E: A sort in the saved search is missing the field name.

Explanation	No additional information is available.
Action	Verify the sort contains a field name.

CWMFS4131E: A condition in the saved search is missing the field name.

Explanation	No additional information is available.
Action	Verify the condition contains a field name.

CWMFS4132E: The condition in the saved search is missing the value.

Explanation	No additional information is available.
Action	Verify the condition has a value.

CWMFS4133E: The saved search name in the URL path: {0} does not match the name in the definition: {1}

Explanation	When you update a saved search by name, the JSON definition name in the request payload must match the name in the URL request.
Action	Verify the same name is used for both definition and the URL. Alternatively, if you are changing the saved search name, use the ID in the URL.

CWMFS4135E: The value of the saved search ''shared'' setting is not valid: {0}; it must be true or false.

Explanation	No additional information is available.
Action	Verify the setting is either true or false.

CWMFS4136E: The saved search must contain a ''name'' setting

Explanation	No additional information is available.
Action	Verify the saved search contains the 'name' setting.

CWMFS4137E: The condition in the saved search is not valid with this combination of field: {0}, operator: {1}, and value: {2}

Explanation	No additional information is available.
Action	Verify the condition is a valid combination of field, operation, and value.

CWMFS4138E: The federated persistence service cannot perform the request because of this error: {0}

Explanation	No additional information is available.
Action	Check the system logs for issues with the federated persistence service.

CWMFS4139E: The federated persistence service is not available.

Explanation	No additional information is available.
Action	Check the system logs for issues with the federated persistence service and the definition of the federated persistence service in the server.xml file.

CWMFS4140E: The user is not authorized to update the saved search: {0}

Explanation	No additional information is available.
Action	Verify that the user belongs to the ACTION_CREATE_SHARED_SAVED_SEARCH or ACTION_ADMINISTER_SHARED_SAVED_SEARCHES action role as defined by the REST service security role.

CWMFS4141E: The user is not authorized to create the saved search: {0}

Explanation	No additional information is available.
Action	Verify that the user belongs to the ACTION_ADMINISTER_SAVED_SEARCHES action role as defined by the REST service security role.

CWMFS4143E: A saved search with this name already exists: {0}

Explanation	No additional information is available.
Action	Change the name.

CWMFS4145E: The user is not authorized to delete this saved search: {0}

Explanation	No additional information is available.
Action	Verify that the user is the owner of the saved search that is being deleted or belongs to the ACTION_ADMINISTER_SHARED_SAVED_SEARCHES action role as defined by the REST service security role.

CWMFS4146E: The user is not authorized to create or update saved searches.

Explanation	No additional information is available.
Action	Assign the user to one of the roles that allows the creation and update of saved searches as defined by the REST service security role.

CWMFS4148E: The saved search name cannot be a number: {0}

Explanation	To avoid confusion with the saved search ID, saved search names cannot be numbers.
Action	Verify that the name is not a number.

CWMFS4149E: A new saved search cannot contain the ''id'' setting: {0}

Explanation	Saved search IDs are assigned by the system. A new saved search cannot contain an 'id' setting.
Action	Verify that the create request does not contain an 'id' setting.

CWMFS4150E: The value of the size setting is not a positive number: {0}

Explanation	No additional information is available.
Action	Verify the size setting is a positive number.

CWMFS4151E: The name cannot be longer than {0} characters

Explanation	No additional information is available.
Action	Verify the name is not longer than the specified number of characters.

CWMFS4152E: The saved search sort field is not valid: {0}

Explanation	No additional information is available.
Action	Verify that the field name exists.

CWMFS4153E: The saved search name must contain viewable characters.

Explanation	No additional information is available.
Action	Verify that the name value contains characters other than spaces.

CWMFS4154E: The saved search name cannot be a reserved name: {0}

Explanation	No additional information is available.
Action	Verify the name.

CWMFS4155E: The saved search condition field: {0} is not valid with this operator: {1}

Explanation	No additional information is available.
Action	Verify the condition is a valid combination of operation and field.

CWMFS4156E: The ''owner'' setting is {0}, which is longer than the maximum number of {1}.

Explanation	No additional information is available.
Action	Verify the owner is not longer then the specified number.

CWMFS4157E: The value of the ID cannot be changed.

Explanation	No additional information is available.
Action	Verify the ID is unchanged.

CWMFS4158E: The user cannot create a private saved search that is owned by someone else.

Explanation	No additional information is available.
Action	Verify the user saved search role or shared settings.

CWMFS4159E: The user cannot create a shared saved search that is owned by: {0}

Explanation	No additional information is available.
Action	Verify the user saved search role or shared settings.

CWMFS4160E: The saved search ''owner'' does not exist on the system: {0}

Explanation	No additional information is available.
Action	Verify the owner exists in the user registry.

CWMFS4161E: The saved search definition attribute ''team'' is not supported.

Explanation	No additional information is available.
Action	Verify the team is not specified in the definition.

CWMFS4162E: An alias in the saved search is missing the field name.

Explanation	No additional information is available.
Action	Verify the aliases contains a field name.

CWMFS4163E: The saved search alias field is not valid: {0}

Explanation	No additional information is available.
Action	Verify that the field name exists.

CWMFS4164E: The saved search alias field is not a business data: {0}

Explanation	No additional information is available.
Action	Verify that the field is a business data.

CWMFS4165E: The saved search alias name is not a valid string: {0}

Explanation	No additional information is available.
Action	Verify that the alias name is a string.

CWMFS4166E: An alias in the saved search is missing the alias name.

Explanation	No additional information is available.
Action	Verify that the aliases contains an alias name.

CWMFS4167E: An alias name contains more than 40 characters: {0}.

Explanation	No additional information is available.
Action	Verify that the alias name length is less than or equal to 40 characters.

CWMFS4168E: The imported saved search must contain a ''{0}'' setting.

Explanation	No additional information is available.
Action	Verify that the saved search contains the appropriate setting.

CWMFS4169E: The content of the input request is not properly formed.

Explanation	No additional information is available.
Action	Verify that the input is correctly formed.

CWMFS4170E: The saved search name ''{0}'' is not unique for import.

Explanation	No additional information is available.
Action	Verify that each saved search name to import is unique.

CWMFS4171E: The id or name {0} refers to a BPD system in version {1} while only versions 8.5.7 onwards are supported.

Explanation	No additional information is available.
Action	Ensure that the federated BPD system is version 8.5.7 or later

CWMFS4172E: The ids or names {0} refer to BPD systems respectively in versions {1} while only versions 8.5.7 onwards are supported.

Explanation	No additional information is available.
Action	Ensure that the federated BPD systems are version 8.5.7 or later

CWMFS4173E: The export of saved search from a BPEL federated system is not supported: {0}

Explanation	No additional information is available.
Action	Ensure that the request from the REST service only applies to a federated BPD system.

CWMFS4174E: The export of saved search from BPEL federated systems is not supported.

Explanation	No additional information is available.
Action	Ensure that the request from the REST service only applies to federated BPD systems.

CWMFS4175E: The user is not authorized to share saved searches.

Explanation	No additional information is available.
Action	Verify that the user belongs to the ACTION_CREATE_SHARED_SAVED_SEARCH or ACTION_ADMINISTER_SHARED_SAVED_SEARCHES action role as defined by the REST service security role.

CWMFS4176E: The saved search definition attribute ''teams'' is only supported for shared saved searches.

Explanation	No additional information is available.
Action	Make sure that the saved search definition attribute ''shared'' is set to true to use the ''teams'' attribute.

CWMFS4177E: The saved search definition attribute ''teams'' is incorrectly formatted.

Explanation	No additional information is available.
Action	Make sure that the saved search definition attribute ''teams'' is an array containing at most one JSON object with at least ''teamId'' string attribute.

CWMFS4178E: The user {0} is not allowed to share a saved search with the team {1}.

Explanation	No additional information is available.
Action	Make sure that the team that you are sharing the saved search with exists and that the owner is a member or manager of this team.

CWMFS4179E: A communication error occured when contacting the remote federated data repository: {0}.

Explanation	No additional information is available.
Action	Make sure that a federated data repository is available for PFS.

CWMFS4180E: The user is not authorized to export saved searches (only users with role adminSavedSearch are authorized to export saved searches).

Explanation	No additional information is available.
Action	Verify that the user have the adminSavedSearch role.

CWMFS4181E: Support for the outputFile parameter has been removed from this REST API: the request should be re issued without this parameter.

Explanation	No additional information is available.
Action	Do not specify the outputFile parameter when exporting saved searches.

CWMFS4182E: {0} is not a supported value for searchType. Supported values are: {1}

Explanation	No additional information is available.
Action	Specify a supported value for searchType.

CWMFS4184E: The request to retrieve a SCIM authorization token failed: {0}.

Explanation	No additional information is available.
Action	Failed to retrieve a SCIM authorization token.

CWMFS4185E: The SCIM request to retrieve the information about user ''{0}'' failed: {1}

Explanation	No additional information is available.
Action	Failed to retrieve user information from SCIM

CWMFS4186E: The request to retrieve a SCIM authorization token did not return the expected ''{0}'' key.

Explanation	No additional information is available.
Action	Failed to retrieve a SCIM authorization token.

CWMFS4187E: The user is not authorized to transfer search queries.

Explanation	No additional information is available.
Action	Verify that the user belongs to the ACTION_SAVED_SEARCH_SUPER_ADMIN action role as defined by the REST service security role.

CWMFS4188E: An error prevented the requested search queries transfer action to be performed: {0}.

Explanation	No additional information is available.
Action	Check the error message in {0} to investigate the issue.

CWMFS4189E: The value of the ''action'' parameter is not valid: {0}.

Explanation	The action should be either start or status.
Action	Verify that the value of the 'action' query parameter is either start, status or abort.

CWMFS4190E: The existing transfer status document is not valid: {0}.

Explanation	No additional information is available.
Action	The document with id "transfer-status" in the Federated Data Repository search queries index is not valid and should be deleted by an administrator.

CWMFS4191I: Search queries transfer started at {0} by {1}

Explanation	No additional information is available.
Action	Signal that a search queries transfer operation was started. {0} is the timestamp of the operation start, {1} is the id of the user that started the operation.

CWMFS4192I: {0} saved searches have been found and are candidate for transfer as reusable search queries.

Explanation	No additional information is available.
Action	After the start of a search queries transfer operation, this message indicates how many saved searches are candidate for transfer as reusable search queries.

CWMFS4193I: Saved search with id {0} and name {1} has been successfully transfered as a reusable search query.

Explanation	No additional information is available.
Action	A transfer operation logs this message for each saved search successfully transfered as a reusable search query.

CWMFS4194W: Cannot transfer saved search with id {0} and name {1} as a reusable search query due to error: {2}

Explanation	No additional information is available.
Action	A transfer operation logs this message for each saved search that could not be transfered as a reusable search query.

CWMFS4195I: Search queries transfer terminated at {0}: {1} saved searches successfully transfered, {2} saved searches not transfered because of errors, {3} saved searches not processed.

Explanation	No additional information is available.
Action	Signals that search queries transfer operation was terminated

CWMFS4196E: An error caused the search queries transfer to stop: {0}.

Explanation	No additional information is available.
Action	Check the error message in {0} to investigate the issue.

CWMFS4197I: Search queries transfer abort requested.

Explanation	No additional information is available.
Action	Signal that an abort of the current search queries transfer has been requested.

CWMFS4198E: A search queries transfer is already in progress. Use the 'status' action to get more information about it, or the 'abort' action to abort it before starting a new one.

Explanation	No additional information is available.
Action	Only one search queries transfer can be run at a time.

CWMFS4200E: The {0} indexer component was not found for the federated system.

Explanation	The indexer component was not found for this federated system.
Action	Verify Process Federation Server has an indexer defined in the server.xml file for each federated system.

CWMFS4201I: The document will be updated into the PFS index.

Explanation	No additional information is available.
Action	A change log entry has been created to have the indexer update the document into the federated data repository

CWMFS4202I: The document will be deleted from the PFS index.

Explanation	No additional information is available.
Action	A change log entry has been created to have the indexer delete the document from the federated data repository

CWMFS4203I: No action is required.

Explanation	No additional information is available.
Action	There is no data for this process or task in the BPM database and in the federated data repository

CWMFS4204E: Process Instance ID is required and must be a positive Long value.

Explanation	A REST API was called without the mandatory processId parameter, or with an erroneous value for this parameter
Action	Provide a positive long value for the processId parameter

CWMFS4205E: Task ID must be a positive Long value.

Explanation	A REST API was called without the mandatory processId parameter, or with an erroneous value for this parameter
Action	Provide a positive long value for the taskId parameter

CWMFS4206E: The system Id provided as argument refers to a BPEL federated system. Updating BPEL documents is not supported.

Explanation	A REST API was called with a systemId parameter referencing a BPEL system while only BPD systems are supported.
Action	Provide the ID of a BPD system for the systemId parameter

CWMFS4207E: No process instance document to update as process instances are not indexed.

Explanation	No additional information is available.
Action	Enable instance indexing on the federated system declaration in server.xml in order to solve the issue.

CWMFS4208E: The Origin header in the REST request does not contain an address that is an allowed origin for the federated system.

Explanation	No additional information is available.
Action	Verify that the ibmPfs_federatedSystem element in the Process Federation Server server.xml file has a configured allowedOrigins attribute.

CWMFS4209E: Cannot find search query with id: {0}

Explanation	No additional information is available.
Action	Verify the id of the search query.

CWMFS4210E: The value of the ''datatype'' parameter is not valid: {0}.

Explanation	The datatype should be either TASKS or INSTANCES.
Action	Verify that the value of the 'datatype' query parameter is either TASKS or INSTANCES.

CWMFS4211E: The value of the ''systemTypes'' parameter is not valid: {0}.

Explanation	No additional information is available.
Action	Verify that the value of the 'systemTypes' query parameter is a space separated list of valid values from Process, BPEL and Case.

CWMFS4300E: The user is not authorized to call any of the management REST API endpoints.

Explanation	No additional information is available.
Action	Verify that the user is granted the pfsAdministrator role.

CWMFS4301E: No federated system matches the federated systems filter ''{0}''

Explanation	No additional information is available.
Action	No action required

CWMFS4500E: Federated System configuration {0} was not found.

Explanation	The ibmPfs_federatedSystem configuration referenced by a BPD retriever in server.xml cannot be found.
Action	No action required

CWMFS4503E: Error when parsing the response from Federated System {0} BPD REST API {1}: {2}

Explanation	An error occurred when parsing the response returned by a federated system BPD REST API
Action	Use the error message {2} to diagnose the issue

CWMFS4508E: Failed to register MBean {0}.

Explanation	Process Federation Server failed to register an MBean for a BPD retriever.
Action	An FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS4509E: Failed to unregister MBean {0}.

Explanation	Process Federation Server failed to unregister the MBean of a BPD retriever.
Action	An FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS4511E: A severe error has occurred in MBean with unique id {0}: {1}

Explanation	No additional information available
Action	In addition to the error message provided in {1}, an FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS4512W: No access token found in incoming request for federated system {0}.

Explanation	No access token found in incoming request for a BPD federated system that is configured in server.xml with an authentication mechanism that requires this kind of token.
Action	Calls to the Process Federation Server REST API must include an access token if federated systems are configured with property authenticationMechanism set to PFS_ACCESS_TOKEN in server.xml

CWMFS4600E: Federated System configuration {0} was not found.

Explanation	The ibmPfs_federatedSystem configuration referenced by a Case retriever in server.xml cannot be found.
Action	No action required

CWMFS4603E: Error when parsing the response from Federated System {0} REST API {1}: {2}

Explanation	An error occurred when parsing the response returned by a Case federated system REST API
Action	Use the error message {2} to diagnose the issue

CWMFS4608E: Failed to register MBean {0}.

Explanation	Process Federation Server failed to register an MBean for a Case retriever.
Action	An FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS4609E: Failed to unregister MBean {0}.

Explanation	Process Federation Server failed to unregister the MBean of a Case retriever.
Action	An FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS4611E: A severe error has occurred in MBean with unique id {0}: {1}

Explanation	No additional information available
Action	In addition to the error message provided in {1}, an FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS4612W: No access token found in incoming request for federated system {0}.

Explanation	No access token found in incoming request for a Case federated system that is configured in server.xml with an authentication mechanism that requires this kind of token.
Action	Calls to the Process Federation Server REST API must include an access token if federated systems are configured with property authenticationMechanism set to PFS_ACCESS_TOKEN in server.xml

CWMFS4706E: Federated System configuration {0} was not found.

Explanation	The ibmPfs_federatedSystem configuration referenced by a BPEL retriever in server.xml cannot be found.
Action	No action required

CWMFS4720E: Not able to get the SSL configuration, please make sure server.xml set any one of 3 options: sslDefault, defaultSSLConfig, defaultKeyStore (contains target federated systems certificates).

Explanation	Process Federation Server cannot retrieve an SSL configuration to use to connect to a federated system.
Action	make sure server.xml set any one of 3 options: sslDefault, defaultSSLConfig, defaultKeyStore (contains target federated systems certificates)

CWMFS4721E: Failed to register MBean {0}.

Explanation	Process Federation Server failed to register an MBean for a BPEL retriever.
Action	An FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS4721W: Timeout setting is set low: {0} milliseconds.

Explanation	Process Federation Server didn't manage to connect to and get and get an answer from a federated system, with a connectTimeout or readTimeout configuration property set to less than 3 seconds in server.xml for a retriever.
Action	Use higher values for the connectTimeout and / or readTimeout configuration attribute of retrievers in server.xml

CWMFS4722E: Failed to unregister MBean {0}.

Explanation	Process Federation Server failed to unregister the MBean of a BPEL retriever.
Action	An FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS4723E: Failed to create MBean for retriever service id {0}: {1}

Explanation	Process Federation Server failed to create the MBean of a BPEL retriever.
Action	Use the error message provided in {1} to diagnose and fix the issue.

CWMFS4724E: A severe error has occurred in MBean with unique id {0}: {1}

Explanation	No additional information available
Action	In addition to the error message provided in {1}, an FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS4725W: No access token found in incoming request for federated system {0}.

Explanation	No access token found in incoming request for a BPEL federated system that is configured in server.xml with an authentication mechanism that requires this kind of token.
Action	Calls to the Process Federation Server REST API must include an access token if federated systems are configured with property authenticationMechanism set to PFS_ACCESS_TOKEN in server.xml

CWMFS4726E: Invocation failed: {0} , cause: {1}

Explanation	Process Federation Server failed to call a federated system.
Action	Use the error message in {0} and the error cause in {1} to diagnose and fix the issue.

CWMFS4800E: The key-values array provided as input is badly formatted: {0}. It must follow this syntax: "key1=value1,key2=value2"

Explanation	The additionalHeaders configuration property of a retriever in server.xml is provided with an unsupported format.
Action	Format the values of all additionalHeaders configuration properties as a comma separated list of key=value entries such as "key1=value1,key2=value2"

CWMFS5011I: Controller {0} for {1}: A change to the pool of available agents detected.

Explanation	Set of registered agents to do work has changed
Action	No action is required.

CWMFS5012I: Controller {0} for {1}: Purging non-responsive agents.

Explanation	Some agents have not responded to requests. They will be removed from the available pool.
Action	No action is required.

CWMFS5013I: Controller {0} for {1}: Acknowledgment received from all agents.

Explanation	All agents acknowledged the last message.
Action	No action is required.

CWMFS5014I: Controller {0} for {1}: Signaling Agent {2} to begin work on partitions {3} through {4}, inclusive.

Explanation	The controller is telling a registered agent to begin work.
Action	No action is required.

CWMFS5015I: Controller {0} for {1}: Removing Agent {2} from the available pool.

Explanation	The controller is removing a particular agent from the pool.
Action	No action is required.

CWMFS5016I: Controller {0} for {1}: Signaling Agent {2} to quiesce.

Explanation	The controller is telling a particular agent to quiesce.
Action	No action is required.

CWMFS5017I: Controller {0} for {1}: Took ownership of the agents.

Explanation	This target has become the controller.
Action	No action is required.

CWMFS5018I: Agent {0} for {1}: Registered with controller.

Explanation	Agent has registered
Action	No action is required.

CWMFS5019I: Agent {0} for {1}: Received a message from the controller.

Explanation	Agent needs to take action.
Action	No action is required.

CWMFS5020I: Agent {0} for {1}: Quiescing.

Explanation	Agent is quiescing.
Action	No action is required.

CWMFS5021I: Agent {0} for {1}: Beginning work on partitions {2} through {3}, inclusive.

Explanation	Agent is beginning work.
Action	No action is required.

CWMFS5022E: Agent for {0}: An error occurred accessing the partitioning agent table: {1}

Explanation	Unable to access the database tables containing the partitioning meta-data.
Action	Review the logs for root cause.

CWMFS5022I: Agent {0} for {1}: Lease lost. Will re-register.

Explanation	Agent has expired. It will re-register.
Action	No action is required.

CWMFS5023E: Controller for {0}: An error occurred accessing the partitioning controller table: {1}

Explanation	Unable to access the database tables containing the partitioning meta-data.
Action	Review the logs for root cause.

CWMFS5024E: Audit log for {0}: An error occurred accessing the partitioning audit log table: {1}

Explanation	Unable to access the database tables containing the partitioning meta-data.
Action	Review the logs for root cause.

CWMFS5025E: Controller for {0}: Attempting to re-initialize due to a severe error: {1}

Explanation	The controller was unable to update it's internal state.
Action	Review the logs for root cause.

CWMFS5026E: Controller for {0}: Shutting down due to severe error: {2}

Explanation	The controller was unable to continue and will shut down.
Action	Review the logs for root cause.

CWMFS5027E: Agent for {0}: Attempting to re-initialize due to a severe error: {1}

Explanation	The agent was unable to update it's internal state.
Action	Review the logs for root cause.

CWMFS5028E: Agent for {0}: Shutting down due to severe error: {2}

Explanation	The agent was unable to continue and will shut down.
Action	Review the logs for root cause.

CWMFS5029W: Agent for {0}: The required table {1} for schema {2} does not exist at data source with URL {3}.

Explanation	A required table does not exist.
Action	Ensure that the required table has been created in specified database for the specified schema.

CWMFS5030W: Controller for {0}: The required table {1} for schema {2} does not exist at data source with URL {3}.

Explanation	A required table does not exist.
Action	Ensure that the required table has been created in specified database for the specified schema.

CWMFS5031I: Target name for the server partitioning service has been set to {0}.

Explanation	Target name for this server's partitioning service has been set. It will be used in column SOURCE_ID of table PFS_BPD_CHANGE_LOG_CONSMR_LOG, in column TARGET of table PFS_PARTITIONING_AGENT and in column TARGET of table PFS_PARTITIONING_CONTROLLER.
Action	No action is required.

CWMFS5032W: A duplicate entry was returned from the database for partitioning agent {0}: entry {1} has been ignored from the query result and entry {2} has been used instead.

Explanation	A same partitioning agent was retrieved twice from the database, which is unexpected: the database query result has been updated to remove the duplicate.
Action	No action is required.

CWMFS6001E: PFS MBean {0} can not be unregistered, exception is {1}.

Explanation	Process Federation Server encountered an exception when unregistering the MBean identified by {0}.
Action	In addition to the exception information provided in {1}, an FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS6002E: Manageable bean type {0} is not supported.

Explanation	Internal error: Process Federation Server was not able to register an MBean because its type is unsupported.
Action	Contact IBM support if this error occurs.

CWMFS6004E: PFS MBean {0} can not be registered, exception is {1}.

Explanation	Process Federation Server encountered an exception when registering the MBean identified by {0}.
Action	In addition to the exception information provided in {1}, an FFDC file with a complete stack trace of the error is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS7000E: An unexpected failure occurred.

Explanation	No additional information available
Action	Refer to the detail of the exception in the logs to identify and fix the issue.

CWMFS7001E: An unexpected exception occurred while building the REST response.

Explanation	No additional information available
Action	Refer to the details of the exception in the logs to identify and fix the issue.

CWMFS7002E: More than one ElasticSearch service has been found.

Explanation	Internal error
Action	Contact IBM support

CWMFS7003E: Cannot find ElasticSearch service.

Explanation	The internal elasticsearch service cannot be found.
Action	Search for errors in the Process Federation Server logs to understand why the internal elasticsearch service has not been created.

CWMFS7004E: Page size must be a positive value.

Explanation	The pageSize attribute of an HTTP request to the Process Federation Server diagnostic tool as an uncorrect value.
Action	Call the diagnostic tool REST API with a positive value for the pageSize attribute.

CWMFS7005E: Cannot find the indexer with index named {0}.

Explanation	The Process Federation Server diagnostic tool cannot find any indexer for index {0}
Action	Provide the name of an index for which an indexer is defined in the server.xml configuration file when calling the diagnostic tool REST API.

CWMFS7006E: Cannot parse JSON body.

Explanation	The Process Federation Server diagnostic tool was unable to parse the body of a request.
Action	Format the body of the request to the diagnostic tool API according to JSON standards.

CWMFS7007E: Empty task list provided as input.

Explanation	The Process Federation Server diagnostic tool was unable to process the request because a task list is missing in the request body.
Action	Add a task list to the request body.

CWMFS7008E: Empty task id list provided as input.

Explanation	The Process Federation Server diagnostic tool was unable to process the request because a task id list is missing in the request body.
Action	Add a task id list to the request body.

CWMFS7009E: {0} cannot be null.

Explanation	The Process Federation Server diagnostic tool found an unexpected null value in the body of a request or in a document retrieved from the federated data repository
Action	Use the value provided in {0} to identify which field has an unexpected null value.

CWMFS7011E: The processing of request with id {0} has been interrupted.

Explanation	The Process Federation Server diagnostic tool was unable to retrieve the result of a processing job because the corresponding thread was interrupted.
Action	Refer to the details of the exception in the logs to identify and fix the issue.

CWMFS7012E: The processing of request with id {0} has failed

Explanation	The Process Federation Server diagnostic tool was unable to retrieve the result of a processing job.
Action	Refer to the details of the exception in the logs to identify and fix the issue.

CWMFS7013E: There is no job with the ID {0}.

Explanation	The Process Federation Server diagnostic tool was unable to stop a processing job because there is none matching the provided job id.
Action	Make sure to provide the id of a job that is currently running.

CWMFS7014E: Cannot parse the BPD task Id: {0}. A BPD task Id must be a positive long value.

Explanation	The Process Federation Server diagnostic tool was unable to parse a BPD task id.
Action	Use a positive long value for BPD task id values.

CWMFS7015E: Cannot parse the BPD process instance Id: {0}. A BPD process instance Id must be a positive long value.

Explanation	The Process Federation Server diagnostic tool was unable to parse a BPD instance id.
Action	Use a positive long value for BPD instance id values.

CWMFS7016E: Cannot parse the BPEL task Id: {0}. A BPEL task Id must be like: "_TKI:01234567.89abcde.fg012345.6789abc".

Explanation	The Process Federation Server diagnostic tool was unable to parse a BPEL task id.
Action	Use format "_TKI:xxxxxxxx.xxxxxxx.xxxxxxxx.xxxxxxx" for BPD instance id values.

CWMFS7017E: The input date is not in the expected format {0} : {1}

Explanation	The Process Federation Server diagnostic tool was unable to parse a date value.
Action	Use the format provided in {0} for the date value.

CWMFS7018E: An error occurred while querying the remote federated data repository: {0}

Explanation	The Process Federation Server diagnostic tool encountered an error when querying the federated data repository
Action	Use the error message in {0} and the stack trace provided in the Process Federation Server logs to diagnose and fix the issue.

CWMFS7019E: Process Instance indexing is not enabled on index {0}

Explanation	The Process Federation Server diagnostic tool was unable to perform the requested operation on index {0} because instance indexing is not enabled for the corresponding federated system.
Action	No action required

CWMFS7020E: Empty task and instance lists provided as input.

Explanation	The Process Federation Server diagnostic tool was unable to process the request because task and instance lists are missing in the request body.
Action	Add a task and instance lists to the request body.

CWMFS8000I: The external federated data repository client component has been activated

Explanation	No additional information available
Action	This message is expected at the start of Process Federation Server.

CWMFS8001I: The external federated data repository client component has been deactivated

Explanation	No additional information available
Action	This message is expected when Process Federation Server stops.

CWMFS8002I: The external federated data repository client component has been updated with the following configuration properties: {0}

Explanation	No additional information available
Action	This message is expected at the start of Process Federation Server of when the federated data repository configuration is updated in server.xml

CWMFS8004I: No username and password combination provided for the external federated data repository client connection, assuming that no authentication is required

Explanation	This message signals that no username and password values are provided in the configuration of the federated data respository in server.xml
Action	No action required

CWMFS8006W: Found {0} system info documents in index {1}, processing the first one

Explanation	The index {1} contains more than one system info document while it is supposed to contains a single one. The federated data respository will use the first one as reference.
Action	A federated system index is supposed to contains a single system info document: remove all documents where field document.subtype equals systeminfo so that a Process Federation Server indexer recreates a single one.

CWMFS8007E: The external federated data repository service returned error response {0} when queried with query {1}

Explanation	No additional information available
Action	Use the federated data respository error response provided in {0} for query {1} to investigate and fix the issue.

CWMFS8008I: Creating index {0} with alias {1}, {2} shards and {3} replicas, with default mapping.

Explanation	The Process Federation Server federated data repository client is creating a new index in the federated data repository
Action	This message is expected when Process Federation Server creates an index for a federated system.

CWMFS8009I: Creating index {0} with alias {1}, {2} shards and {3} replicas, with no default mapping

Explanation	The Process Federation Server federated data repository client is creating a new index in the federated data repository, without any default mappings
Action	No action required

CWMFS8010W: Index name {0} does not match any input alias name: using the actual index name in the search result

Explanation	The Process Federation Server data repository client is not able to find the alias of an index.
Action	No action required

CWMFS8011E: The following date retrieved from the federated data repository failed to be parsed {0}

Explanation	The Process Federation Server data repository client is unable to parse the value of a date retrieved from an indexed document.
Action	No action required

CWMFS8012I: Deleting alias {0} from index {1}

Explanation	The Process Federation Server data repository client is deleting an index alias.
Action	No action required

CWMFS8013I: Deleting index {0}

Explanation	The Process Federation Server data repository client is deleting an index.
Action	No action required

CWMFS8014I: Index {0} already exists, creation cancelled.

Explanation	Creation of an index that already exist was requested to the Process Federation Server federated data repository client.
Action	No action required

CWMFS8015W: Remote federated data repository cluster is {0} version {1}, which is not supported: version should be at least {2} and less than {3}

Explanation	The federated data repository has an unsupported version.
Action	Use a supported version of Elasticsearch or Opensearch as the federated data repository.

CWMFS8016I: Remote federated data repository cluster is {0} version {1}

Explanation	This message is displayed the first time that Process Federation Server connects to the federated data repository and provide information about the federated data repository vendor and version.
Action	No action required

CWMFS8017W: The document in the index "{0}" with id "{1}" contains the following field: "{2}". The _ignored field indexes and stores the names of every field in a document that has been ignored when the document was indexed. This can, for example, be the case when a keyword field value length exceeds the ignore_above setting. When indexing a string field, the Elasticsearch default dynamic mapping rules create a sub keyword field that sets ignore_above: 256. Sorted queries based on one of the fields mentioned in the value of the _ignored field will return this document at the end of the list.

Explanation	Process Federation Server found a document with an _ignored field when performing an index search.
Action	No action required

CWMFS8018W: Remote federated data repository cluster is {0} version {1}, which is deprecated: supported versions that are not deprecated starts at {2}

Explanation	The federated data repository has a deprecated version.
Action	Use a supported version of Elasticsearch or Opensearch as the federated data repository.

CWMFS8019W: Remote federated data repository configuration parameter {0} does not apply to this version of Process Federation Server, the values provided in server.xml will be ignored.

Explanation	No additional information available
Action	The corresponding configuration attributes can be removed from the server.xml configuration file.

CWMFS8020I: Deletion request for document {0} in index {1} was ignored because the document does not exist

Explanation	Deletion of a document that does not exist was requested to the Process Federation Server federated data repository client.
Action	No action required

CWMFS8021E: Unknown attribute {0} in JSON search query

Explanation	A JSON search query has an unknown attribute.
Action	Remove the unknown attribute from the JSON search query.

CWMFS8022E: Illegal value for attribute {0} in JSON search query

Explanation	A JSON search query has an attribute with an illegal value (a number instead of a string, an unknown constant, etc...).
Action	Update the value of the attribute in the JSON search query to provide a supported one.

CWMFS8023E: Error when parsing the JSON search query: {0}

Explanation	An error occurred when parsing a JSON search query
Action	Use the error details provided in {0} to fix the issue.

CWMFS8024E: Field name {0} is not valid

Explanation	A field name referenced in the search query is not valid
Action	No action required

CWMFS8025E: Operator {1} cannot be used in a condition on field {0}

Explanation	No additional information is available.
Action	Fix the condition to use a valid combination of operator and field.

CWMFS8026E: Value {2} cannot be used for condition on field {0} with operator {1}

Explanation	No additional information is available.
Action	Fix the condition to use a valid combination of field, operator, and value.

CWMFS8027E: Error when validating the search query: {0}

Explanation	An error occurred when validating a search query
Action	Use the error details provided in {0} to fix the issue.

CWMFS8028E: List of sharing teams can only be specified on a shared search query.

Explanation	A list of teams to share a search query with was provided for an unshared search query
Action	Either remove the list of teams or set metadata.sharing.shared to true

CWMFS8029E: teamId attribute is missing for team {0}.

Explanation	A teamId attribute is missing in a team definition
Action	Add the missing teamId attribute to the team definition

CWMFS8030E: id attribute is missing for user {0}.

Explanation	the id attribute is missing in a user definition
Action	Add the missing id attribute to the user definition

CWMFS8031E: Cannot parse date value {0} for attribute {1}.

Explanation	A date attribute cannot be parsed
Action	Format the date as YYYY-MM-DDTHH:mm:ss.SSSZ

CWMFS8032E: Failure reported by the federated data repository when creating, updating or deleting search queries: {0}.

Explanation	A failure has been reported by the federated data repository when creating, updating or deleting a search query
Action	Use the failure details provided in {0} to further analyze the issue.

CWMFS8033E: Cannot persist a search query with this name, please use another unique name.

Explanation	The name provided for the search query is not unique and cannot be used to persist it.
Action	Provide another name that is unique across persisted search queries.

CWMFS8034E: An unexpected error occurred when retrieving, creating, updating or deleting search queries: {0}.

Explanation	No additional information is available.
Action	Use the error details provided in {0} to further analyze the issue.

CWMFS8035E: An unexpected error occurred when initializing the federated data repository index that stores search queries: {0}.

Explanation	No additional information is available.
Action	Use the error details provided in {0} to further analyze the issue.

CWMFS8036E: An unexpected error occurred when generating an id for a search query: {0}.

Explanation	No additional information is available.
Action	Use the error details provided in {0} to further analyze the issue.

CWMFS8037E: The user is not authorized to create or update reusable search queries.

Explanation	No additional information is available.
Action	Assign the user to one of the roles that allows the creation and update of search queries as defined by the REST service security roles.

CWMFS8038E: Attribute {0} is missing in the search query.

Explanation	A mandatory attribute is missing in the search query
Action	Add the missing attribute to the search query and try again.

CWMFS8039E: The search query name cannot be a number.

Explanation	To avoid confusion with a search query ID, reusable search query names cannot be numbers.
Action	Verify that the name is not a number.

CWMFS8040E: The user is not authorized to share search queries.

Explanation	No additional information is available.
Action	Assign the user to one of the roles that allows sharing search queries as defined by the REST service security roles.

CWMFS8041E: User is not authorized to assign a shared search query to another user.

Explanation	No additional information is available.
Action	Grant the user to one of the roles that allows assigning shared search queries to another user, as defined by the REST service security roles.

CWMFS8042E: User is not authorized to assign an unshared search query to another user.

Explanation	No additional information is available.
Action	Grant the user to one of the roles that allows assigning unshared search queries to another user, as defined by the REST service security roles.

CWMFS8043E: {0} is not a valid user id for attribute {1}: cannot find an existing user with this id.

Explanation	No additional information is available.
Action	Replace the faulty user id with the id of an actual user.

CWMFS8044E: A search query can only be shared with a single team (or with everybody).

Explanation	No additional information is available.
Action	Reference a single team (or none) in sharing metadata.

CWMFS8045E: The search query cannot be shared with team {0}.

Explanation	No additional information is available.
Action	Use the globalTeams metadata REST API to retrieve the list of teams that you are authorized to share search queries with.

CWMFS8046E: No index available to process the search query.

Explanation	No index is matching the datasource of the search query.
Action	Update the datasource of the search query so that it matches at least one existing index.

CWMFS8047E: The user is not authorized to get, update or delete this reusable search queries.

Explanation	No additional information is available.
Action	The user is not the owner of the search query and has not been granted a role that allows managing queries owned by other people.

CWMFS8048E: Search query {0} cannot be found.

Explanation	No additional information is available.
Action	Check that the provided id references an existing search query.

CWMFS8049E: Search query attribute {0} cannot be modified by an extension.

Explanation	Update the extension to remove the offending attribute.
Action	When extending a search query it is not possible to change the value of certain attribute.

CWMFS8050E: Search query datasource extension can only provide a subset of the existing systemTypes: {0}.

Explanation	Update the extension to use a subset of the existing systemTypes.
Action	When extending a search query it is only possible to use a subset of the existing datasource.systemTypes attribute.

CWMFS8051E: MANAGED_TEAMS population target can only be used with TASKS datasources.

Explanation	No additional information is available.
Action	Use another population target.

CWMFS8052E: Missing attribute {0} in JSON search query

Explanation	A JSON search query has a missing mandatory attribute.
Action	Define the mandatory attribute in the JSON search query.

CWMFS8053E: The JSON search query format does not match the JSON search query extension format

Explanation	A JSON search query can only be extended using the same json format version.
Action	Ensure that the json format of the extension matches the json format of the query to extend

CWMFS8054E: A JSON search query with "datasource.datatype" set to "INSTANCES" cannot reference an output field with "kind" set to "Task"

Explanation	A JSON search query of instances cannot output a field defined at the task level
Action	Ensure that the field list does not contain any field defined at the task level

CWMFS8055E: A JSON search query with "datasource.datatype" set to "INSTANCES" cannot be sorted on a field with "kind" set to "Task"

Explanation	A JSON search query of instances cannot sort on a field defined at the task level
Action	Ensure that enhanced search query is not configured to sort on a field defined at the task level

CWMFS8056E: A JSON search query using format {0} must not reference the following attribute: {1}

Explanation	One of the attributes of the enhanced search query is not supported in the current JSON format
Action	Ensure that enhanced search query is conforming to the JSON format specified as "jsonFormat" key

CWMFS8057E: {0} population target is not allowed.

Explanation	No additional information is available.
Action	Use a supported population target.

CWMFS8058E: The user is not authorized to retrieve reusable search queries owned by other users.

Explanation	No additional information is available.
Action	The user must have full administration privileges on reusable search queries.

CWMFS8250E: Error parsing the JSON response from {0} server: {1}

Explanation	The Process Federation Server federated data repository client encountered an error when parsing a response from the federated data repository.
Action	Gather more information about the error in the Process Federation Server logs.

CWMFS8251E: Error occurred serializing a request

Explanation	The Process Federation Server federated data repository client encountered an error when serializing a request to the federated data repository
Action	Gather more information about the error in the Process Federation Server logs.

CWMFS8252E: Error occurred serializing a response

Explanation	The Process Federation Server federated data repository client encountered an error when serializing a response.
Action	Gather more information about the error in the Process Federation Server logs.

CWMFS8253W: Failure on endpoint {0}: {1}. Will not retry before at least {2} seconds.

Explanation	The Process Federation Server federated data repository client detected a failure on the federated data repository endpoint {0} and will not try to use it again for at least {2} seconds.
Action	In addition to the failure displayed in the message at {1}, an FFDC file with a complete stack trace of the failure is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the cause.

CWMFS8254I: Cluster Availability Monitor Daemon has started

Explanation	The daemon thread that monitors the availability of the federated data repository endpoints has started.
Action	This message is expected when Process Federation Server is starting.

CWMFS8255E: Exception occurred in the availability monitor

Explanation	An exception occurred in the daemon thread that monitors the availability of the federated data repository endpoints
Action	Process Federation Server need to be restarted in order to reconnect to the federated data repository. In addition to the error displayed in the message at {1}, an FFDC file with a complete stack trace of the failure is generated in the logs/ffdc sub directory of the Process Federation Server directory to help diagnose the error cause.

CWMFS8256I: Cluster Availability Monitor Daemon has stopped

Explanation	The daemon thread that monitors the availability of the federated data repository endpoints has stopped.
Action	This message is expected when Process Federation Server stops. In all other situations, Process Federation Server must be restarted in order to re connect to the federated data repository.

CWMFS8257I: Cluster Availability Monitor Daemon has been requested to stop

Explanation	The daemon thread that monitors the availability of the federated data repository endpoints has been requested to stop.
Action	This message is expected when Process Federation Server stops.

CWMFS8258W: Endpoint {0} with cluster info {1} cannot be added to current cluster with info {2}

Explanation	The federated data repository is configured in the server.xml configuration file with a list of endpoints to nodes that are not part of a same Elasticsearch or Opensearch cluster.
Action	Update the endpoints parameters of the federated data repository in server.xml so that all endpoint URLs are to nodes of the same Elasticsearch of Opensearch cluster.

CWMFS8259I: Setting endpoint {0} with cluster info {1} as available

Explanation	The daemon thread that monitors the availability of the federated data repository endpoints has set one of the endpoints as available.
Action	No action required

CWMFS8260W: Endpoint {0} not found in unavailable endpoints queue

Explanation	Internal error: The daemon thread that monitors the availability of the federated data repository endpoints was unable to remove an available endpoint from the list of unavailable endpoints because this endpoint was not in the list.
Action	No action required

CWMFS8261W: Setting endpoint {0} as unavailable

Explanation	The daemon thread that monitors the availability of the federated data repository endpoints has set one of the endpoints as unavailable.
Action	No action required

CWMFS8262W: Endpoint {0} not found in available endpoints queue

Explanation	Internal error: The daemon thread that monitors the availability of the federated data repository endpoints was unable to remove an unavailable endpoint from the list of available endpoints because this endpoint was not in the list.
Action	No action required

CWMFS8500I: Activating the DBA registry client component

Explanation	No additional information available
Action	This message is expected at the start of a Process Federation Server container in Kubernetes.

CWMFS8501I: Deactivating the DBA registry client component

Explanation	No additional information available
Action	This message is expected when a Process Federation Server container in Kubernetes is stopping.

CWMFS8502I: Updating the DBA Registry client component with the following configuration properties: {0}

Explanation	No additional information available
Action	This message is expected at the start of a Process Federation Server container in Kubernetes.

CWMFS8503E: Missing configuration parameter {0}

Explanation	Process Federation Server container DBA registry client found a missing configuration parameter in a DBA resource registry entry.
Action	No action required

CWMFS8504W: Ignoring key {0} because an error occurred processing it: {1}

Explanation	Process Federation Server container DBA registry client encoutered an error processing the entry with key {0} in the DBA resource registry.
Action	No action required

CWMFS8505I: Removing federated system: {0}

Explanation	Process Federation Server container DBA registry client is removing a federated system entry from the Process Federation Server configuration because the corresponding key was removed from the DBA resource registry.
Action	No action required

CWMFS8506I: Deleting {0} configuration file

Explanation	Process Federation Server container DBA registry client is removing a configuration file.
Action	No action required

CWMFS8507E: Deletion of {0} failed: {1}

Explanation	Process Federation Server container DBA registry client failed to delete a file.
Action	Use the error provided in {1} to diagnose the cause of the failure.

CWMFS8508E: Exception while watching for {0} Resource Registry key: {1}

Explanation	Process Federation Server container DBA registry client encountered an error while watching the key {0} in the DBA resource registry.
Action	Use the error provided in {1} to diagnose the cause of the error.

CWMFS8509E: Exception while waiting

Explanation	Process Federation Server container DBA registry client encountered an error while waiting between keys watch.
Action	Use the error details provided in the Process Federation Server container logs to diagnose the cause of the error.

CWMFS8510E: Parse error on key {0}, exception while parsing the following value: {1} (error message: {2})

Explanation	Process Federation Server container DBA registry client encountered an error when parsing the value {1} retrieved in the DBA resource registry under key {0}.
Action	Use the error message provided in {2} to diagnose the cause of the error.

CWMFS8511E: {0} is not a supported system type

Explanation	An entry in the DBA resource registry has an unsupported value for system type.
Action	No action required

CWMFS8512W: The Federated System Retriever thread could not be gracefully stopped: {0}

Explanation	Process Federation Server container DBA registry client did not managed to gracefully stop its federated system retriever thread while stopping.
Action	No action required

CWMFS8513E: The Federated System Retriever thread could not be cancelled: {0}

Explanation	Process Federation Server container DBA registry client did not managed to cancel its federated system retriever thread while stopping.
Action	No action required

CWMFS8514I: Stopping the Federated System Retriever thread...

Explanation	Process Federation Server container DBA registry client is stopping its federated system retriever thread
Action	No action required

CWMFS8515I: The Federated System Retriever thread has been stopped

Explanation	Process Federation Server container DBA registry client has stopped its federated system retriever thread
Action	No action required

CWMFS8516I: Exiting Federated System Retriever thread...

Explanation	The federated system retriever thread of the Process Federation Server container DBA registry client has stopped
Action	No action required

CWMFS8517I: The {0} federated system configuration is unchanged

Explanation	Process Federation Server container DBA registry client detected that an entry updated in the DBA resource registry has the same value than before and will ignore the update.
Action	No action required

CWMFS8518I: Updating the {0} federated system configuration: {1}

Explanation	Process Federation Server container DBA registry client detected that an entry updated in the DBA resource registry has a different value than before and will update the federated system configuration accordingly.
Action	No action required

CWMFS8519I: Key {0} has been identified as referencing an on-premise federated system

Explanation	Process Federation Server container DBA registry client detected that an entry in the DBA resource registry is referencing an on premise BAW server.
Action	No action required

CWMFS8520I: Ignoring key {0} because the seamless federation is not requested

Explanation	Process Federation Server container DBA registry client detected that an entry in the DBA resource registry has its federate attribute set to false and will ignore it.
Action	No action required

CWMFS9000E: No URL found in service registry client configuration

Explanation	Error in the Process Federation Server container DBA registry client configuration: the URL to the DBA resource registry is missing.
Action	No action required

CWMFS9001E: No password found in service registry client configuration

Explanation	Error in the Process Federation Server container DBA registry client configuration: the password to access the DBA resource registry is missing.
Action	No action required

CWMFS9002I: No credentials found in service registry client configuration, connecting anonymously

Explanation	The Process Federation Server container DBA registry client configuration does not contains credentials to connect to the DBA resource registry.
Action	No action required

CWMFS9003E: Could not connect to the service registry: {0}

Explanation	Process Federation Server container DBA registry client failed to connect to the DBA resource registry.
Action	Use the error message provided in {Ø} to diagnose the issue.

CWMFS9004E: Exception while reading {0} service registry key: {1}

Explanation	Process Federation Server container DBA registry client encountered an error when reading an entry in the DBA resource registry.
Action	Use the error message provided in {1} to diagnose the issue.

CWMFS9005I: Service registry watch started on key: {0}

Explanation	Process Federation Server container DBA registry client has started watching DBA resource registry key {0}.
Action	No action required

CWMFS9006I: Service registry watch stopped on key: {0}

Explanation	Process Federation Server container DBA registry client has stopped watching DBA resource registry key {0}.
Action	No action required

CWMFS9007E: Exception while watching {0} service registry key ({1}): {2}

Explanation	Process Federation Server container DBA registry client encountered an error when watching DBA resource registry key {0}.
Action	Use the error message provided in {2} to diagnose the issue.

CWMFS9008E: The query to {0} returned an unexpected HTTP response code : {1}

Explanation	Process Federation Server container DBA registry client received an unexpected HTTP response code from the DBA resource registry.
Action	No action required

CWMFS9009E: Unexpected error parsing {0}

Explanation	Internal error: Process Federation Server container DBA registry client encountered an error when parsing the value {0} found in the DBA resource registry.
Action	No action required

CWMFS9010I: Service registry event of type {0} received while watching on "{0}" key

Explanation	Process Federation Server container DBA registry client received an event of type {0} when watching the DBA resource registry key {0}.
Action	No action required

CWMFS9011I: Service registry event received while watching on {0} service registry key

Explanation	Process Federation Server container DBA registry client received an untyped event when watching the DBA resource registry key {0}.
Action	No action required

CWMFS9012W: Service registry key not found: {0}

Explanation	Process Federation Server container DBA registry client coudn't find key {0} in the DBA resource registry
Action	No action required

CWMFS9013E: The {0} service registry key is already watched

Explanation	Internal error: Process Federation Server container DBA registry client got a request to watch a key that it is already watching.
Action	No action required

CWMFS9014E: Member with id = {0} returned an obsolete revision number. Returned {1} while expecting revision {2} or greater

Explanation	Process Federation Server container DBA registry client received an outdated response from the DBA resource registry.
Action	No action required

CWMFS9015E: The watch query on "{0}" service registry key was not created

Explanation	Process Federation Server container DBA registry client failed to register a watch on the DBA resource registry.
Action	No action required

CWMFS9016I: Service registry key found: {0}

Explanation	Process Federation Server container DBA registry client found entry with key {0} in the DBA resource registry.
Action	No action required

CWMFS9017I: Connection lost with DBA Registry. Reconnecting...

Explanation	Process Federation Server container DBA registry client lost its connection with the DBA resource registry and is reconnecting.
Action	No action required

CWMFS9500I: Activating the Notification Listener component

Explanation	No additional information available
Action	No action required

CWMFS9501I: Deactivating the Notification Listener component

Explanation	No additional information available
Action	No action required

CWMFS9502I: Updating the Notification Listener component with the following configuration properties: {0}

Explanation	No additional information available
Action	No action required

CWMFS9503I: Updated the Notification Listener component with the following configuration properties: {0}

Explanation	No additional information available
Action	No action required

CWMFS9504E: Missing mandatory child element: {0}

Explanation	No additional information available
Action	No action required

CWMFS9505E: Missing mandatory property {0} in child element {1}

Explanation	No additional information available
Action	No action required

CWMFS9506I: Stopping the Notification Listener Daemon: {0}

Explanation	No additional information available
Action	No action required

CWMFS9507E: Throwable while starting the Notification Listener: {0}

Explanation	No additional information available
Action	No action required

CWMFS9508E: Throwable while cleaning the Notification Listener ({0}): {1}

Explanation	No additional information available
Action	No action required

CWMFS9509W: Could not retrieve JMS TopicConnectionFactory and/or JMS Topic from JNDI. Retrying in {0} seconds...

Explanation	No additional information available
Action	No action required

CWMFS9510I: Creating JMS Connection: {0}

Explanation	No additional information available
Action	No action required

CWMFS9511I: Creating JMS Session:: {0}

Explanation	No additional information available
Action	No action required

CWMFS9512I: Creating JMS Consumer on topic: {0}

Explanation	No additional information available
Action	No action required

CWMFS9513I: Starting Listening to messages: {0}

Explanation	No additional information available
Action	No action required

CWMFS9514E: Exception while listening to notifications: {0} */

Explanation	No additional information available
Action	No action required

CWMFS9601E: The REST request to {0} returned {1} with agent {2}

Explanation	No additional information available
Action	No action required

CWMFS9603E: Error while trying to get access token: {0}

Explanation	No additional information available
Action	No action required

CWMFS9604E: Cannot parse the following REST API response returned by the retrieval agent {0} after calling {1} {2} : {3}

Explanation	No additional information available
Action	No action required

CWMFS9605E: Cannot find {0} key in the following JSON object: {1}

Explanation	No additional information available
Action	No action required

CWMFS9606E: Exception while calling retrievers: {0}

Explanation	No additional information available
Action	No action required

CWMFS9607E: There is no notification listener associated to a federated system

Explanation	No additional information available
Action	No action required

CWMFS9608E: There is no retriever for federated system {0}

Explanation	No additional information available
Action	No action required

CWMFS9609E: Exception while checking authorization: {0}

Explanation	No additional information available
Action	No action required

CWMFS9610E: Exception faced when trying to retrieve the Rest config

Explanation	No additional information available
Action	No action required

CWMFS9611E: The is associated with an unsupported federated system with id {0}. Notifications are only supported for BPD systems.

Explanation	No additional information available
Action	No action required

CWMFS9612E: OSGI context returned a null service reference.

Explanation	No additional information available
Action	No action required

CWMFS9800E: scimUsername and scimPassword must not be null when scimUrl property is not null.

Explanation	If SCIM must be used to check if a user exists, credentials to the SCIM API are required.
Action	Verify the properties.