Outbound REST Message call getting "Error executing REST request: Error constructing Encrypter"Issue Running a custom workflow activity for a REST Message and it will fails with showing the follow error: "Error executing REST request: Error constructing Encrypter". And there're nothing in the ECC Queue or the Outbound HTTP Requests logs--in other words, no REST message is ever being generated. If you're tailing to the nodelog, you will see the following warning message. 2022-02-14 15:01:17 (453) Default-thread-2 4D4D43EB1BE1415449E7B9DE034BCB96 txid=c2162ba31b61 WARNING *** WARNING *** web_service_message_label is not a valid property for RestMessageProvider_Input2022-02-14 15:01:17 (453) Default-thread-2 4D4D43EB1BE1415449E7B9DE034BCB96 txid=c2162ba31b61 WARNING *** WARNING *** web_service_message_function_label is not a valid property for RestMessageProvider_Input2022-02-14 15:01:17 (453) Default-thread-2 4D4D43EB1BE1415449E7B9DE034BCB96 txid=c2162ba31b61 WARNING *** WARNING *** credentials_label is not a valid property for RestMessageProvider_Input2022-02-14 15:01:17 (453) Default-thread-2 4D4D43EB1BE1415449E7B9DE034BCB96 txid=c2162ba31b61 WARNING *** WARNING *** protocol_profile_label is not a valid property for RestMessageProvider_Input2022-02-14 15:01:17 (453) Default-thread-2 4D4D43EB1BE1415449E7B9DE034BCB96 txid=c2162ba31b61 WARNING *** WARNING *** oauth_entity_profile_label is not a valid property for RestMessageProvider_Input2022-02-14 15:01:17 (579) Default-thread-2 4D4D43EB1BE1415449E7B9DE034BCB96 txid=c2162ba31b61 DEBUG: Invoking REST Service: global.(AF) AutoSys Job Query method:AEWS/job method (PreProd)2022-02-14 15:01:17 (614) Default-thread-2 4D4D43EB1BE1415449E7B9DE034BCB96 txid=c2162ba31b61 WARNING *** WARNING *** string may not be encrypted : Input length must be multiple of 8 when decrypting with padded cipher2022-02-14 15:01:17 (615) Default-thread-2 4D4D43EB1BE1415449E7B9DE034BCB96 txid=c2162ba31b61 SEVERE *** ERROR *** REST Msg Outbound - MIDRESTRequestDispatcher : Error constructing EncrypterCauseThe key that is created by system on ecc_encryption_key table seem to be corrupted with either no key value in it or have some special characters in it when show xml.Resolution-Export the corrupt key (just in case if you need to review that later) -Log on another good working instance and export this same key (you could compared the sys_id to make sure they are the same). -Log back into the not working instance and import this new download key -Once it done, ran the test again and you will not seein the error again.