MuleSoft · Object Store Connector
OS:KEY_NOT_FOUND
OS:KEY_NOT_FOUND means an Object Store Retrieve or Remove operation asked for a key that has no value in the store. Check that the key exists first with Contains, or give Retrieve a default value.
VerifiedLast verified
01Error text
Error type: OS:KEY_NOT_FOUND02Likely causes
- Remove: no value exists for the key.
- Retrieve: no value exists for the key, and the default value parameter was not provided or resolved to null.
03How to fix it
- Confirm that the Store and the Retrieve or Remove operation use the same key expression and the same object store.
- Give the Retrieve operation a default value, which it returns when the key is absent.
- Or call the Contains operation first and only retrieve or remove the key when it is present.
- Handle the failure with an error handler of type
OS:KEY_NOT_FOUNDwhen a missing key is a normal case, such as a first run.
iNotes
The same connector throws OS:KEY_ALREADY_EXISTS from Store when Fail If Present is true and the key is already in the store, and OS:NULL_VALUE when the value is null and Fail On Null Value keeps its default of true.
04Official documentation
→Related errors
- MULE:EXPRESSIONMULE:EXPRESSION means an error occurred while Mule evaluated a DataWeave expression. Find the expression named in the log, check the values it reads for nulls or wrong types, and add a default or a handler.
- VM:QUEUE_TIMEOUTVM:QUEUE_TIMEOUT means a VM Connector operation waited for a queue longer than its Timeout, which is 5 seconds by default. Raise the Timeout, or make the flow that consumes the queue finish sooner.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer