• DOCUMENTATION
  • WORKATO BLOG
  • PRODUCT BLOG
  • Return to Workato
  • Log in
  • ☰
  • Community/Discussions
Solution home Recipe 101 General Best Practices

Best Practices: How to make sure your recipe is using the most updated trigger data

Modified on: Tue, Aug 8, 2017 at 9:41 AM

In Workato, when you run a job in your recipe, your trigger data will always remain the same, even if you rerun your recipe. For example, if you trigger a recipe when a Salesforce opportunity is Created/Updated, and you rerun that particular job after you make changes to that particular opportunity (eg changed the stage or name), the changes will not be reflected in your recipe unless you have the appropriate logic. This use case usually occurs when you are doing troubleshooting using a single job, and you need to make changes to the object that triggers the job. 


To do this, you can run a search step immediately after the trigger using something unique and fixed to that particular object, most likely the ID of the object. This ensures that you have the most updated data in your recipe steps. Do note that you should use the data from the search step for mapping instead of the trigger data, and you may need to re-map some fields in your recipe. 

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.

Related Articles

    Still can't find your solution?

    Visit our forums to search for answers, or post your own questions.

    Documentation
    Developer's Library
    Tutorials
    eBooks
    Product Hour
    Product Blog
    Workato Blog
    Product updates
    Customer Stories
    © Workato 2020   Privacy   Terms   +1 (844) 469-6752
    • Documentation
    • Workato Blog
    • Product Blog
    • Solutions
    • Forums
    • Tickets
    • Log in
    • Return to Workato