Skip to main content
All CollectionsFAQs
Troubleshoot: My time-based workflow isn't firing
Troubleshoot: My time-based workflow isn't firing

Simple fixes to make sure your time-based workflow stays on time

Gauransh Vaishnav avatar
Written by Gauransh Vaishnav
Updated over a year ago

Reasons why your Time-based workflow is not firing:

  1. The Time-based workflow does not fire retroactively.

    This means you will receive alerts for old Salesforce records only if they have been edited or created after setting up this Rattle.
    โ€‹

  2. The Salesforce queue backlog has not been cleared.

    If you would like to edit a live time-based workflow, you will first need to clear the queue in your Salesforce instance. Here's how:

    1. Log in to your Salesforce account.

    2. Go to Setup and navigate to Environments > Monitoring > Time-based workflows. You can also use the quick find search bar to jump directly to Time-based workflows.

    3. Find your Rattle workflow by using the filter option for Workflow rule, Flow, or Process name. Select the 'contains' condition, and enter your Rattle workflow ID (the first 4 digits are enough)in the third field. Hit search.

    4. The list will now display records that meet the Rattle workflow conditions, which are queued to fire.

    5. Delete the records in the list and refresh the page.
      โ€‹

    Return to your Rattle account, and you should now be able to edit and save your workflow with the new conditions.

Finding your Rattle workflow ID

As of October 2022, in response to Salesforce beginning the process of sunsetting workflow rules, an architectural change was made in Rattle so that all newly created Rattles would leverage Flows instead of Workflow Rules. However, these steps are a workaround to utilizing Workflows for Rattles.

  • If you don't see results by searching with the name of your time-based rattle, then use the Rattle workflow ID, shown below.

  • Open your Rattle Workflow and copy the URL code from the search bar. The ID is the alphanumeric code between the forward slash "/" and the question mark "?".

SEE ALSO

Did this answer your question?