# How can I confirm a workflow saved the object before using it later?

Canonical URL: https://help.iagenify.com/faqs/object-storage/how-can-i-confirm-a-workflow-saved-the-object-before-using-it-later

[← Back to Object Storage FAQs](https://help.iagenify.com/faqs/object-storage)

HELP CENTER · FAQ Object Storage 2 min read
# How can I confirm a workflow saved the object before using it later?
Use the save step's returned key and metadata as evidence that the step completed, then have the next step read that exact key. Check the run output before assuming a file exists at the intended path.
IaGenify
Object Storage

## Check the save result, not only the workflow status
A workflow can fail after saving an object if a later step has a problem. In that case, the overall run may be failed even though the save step succeeded. Inspect the step-level result and look for the returned object key, size, and content type to determine what completed.
If the save step itself failed, do not pass an assumed key to later actions. Review its error and the selected storage connection, path, and content input. A path written in the workflow definition is only a requested destination; it is not proof that the object was stored.
## Read back the exact object and verify its content
Pass the returned key to a read or processing step supported by the same storage connection. Confirm that the retrieved content is the expected file and that its size and content type make sense. Do not construct a public URL from the key unless the storage setup explicitly provides that access path.
When a run is retried, check whether the save operation wrote to the same key or a new one, according to the workflow's path choice. Keep the key with the run record so you can investigate downstream errors without guessing which object was produced. [← Back to Object Storage FAQs](https://help.iagenify.com/faqs/object-storage)