Workflows
In some embodiments, after receiving event data corresponding to an event-based workflow, the computer system attempts to cause execution of the first step corresponding to one or more events; and in response to receiving an indication that execution of the first step corresponding to the one or more events has failed, the computer system resolves failure the first step in a manner that is based one or more execution criteria (e.g., failure criteria) that is associated with the first step.
1. A computer system, comprising:
one or more processors; and
memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for:
identifying electronic data corresponding to an event-based workflow, the electronic data including data corresponding to a first step corresponding to one or more events and data corresponding to a second step corresponding to the one or more events, wherein the first step is different from the second step;
after receiving event data corresponding to the event-based workflow, attempting to cause execution of the first step corresponding to the one or more events; and
in response to receiving an indication that execution of the first step corresponding to the one or more events has failed:
in response to determining that the first step is associated with a first set of one or more execution criteria, resolving failure of the first step in a first manner that corresponds to the first set of one or more execution criteria; and
in response to determining that the first step is associated with a second set of one or more execution criteria that is different from the first set of one or more execution criteria, resolving failure of the first step in a second manner that corresponds to the second set of one or more execution criteria, wherein the second manner is different from the first manner.
2. The computer system of claim 1 , wherein the first set of one or more execution criteria or the second set of one or more execution criteria is defined as being related to the first step, and wherein the one or more programs include instructions for:
after resolving failure of the first step, attempting to cause execution of the second step corresponding to the one or more events; and
in response to receiving an indication that execution of the second step corresponding to the one or more events has failed, resolving failure of the second step in a third manner that corresponds to a third set of one or more execution criteria, wherein the third set of one or more execution criteria is not defined as being related to the first step.
3. The computer system of claim 1 , wherein the event-based workflow is a modified version of a preexisting event-based workflow,
wherein the first step is an addition, to the preexisting event-based workflow, made by a third-party that is not the creator of the preexisting event-based workflow, and
wherein the second step is present in the preexisting event-based workflow and is created by the creator of the preexisting event-based workflow.
4. The computer system of claim 1 , wherein resolving failure of the first step in the first manner includes disabling the first step, and wherein the one or more programs include instructions for:
in conjunction with disabling the first step, sending one or more notifications to one or more users, who have indicated that the first step should be performed, that the first step has been disabled.
5. The computer system of claim 1 , wherein:
in accordance with a determination that data corresponding to the first step is a first type of data and data corresponding to the second step is a second type of data that is different from the first type of data, the first step is required to be performed by a first server and the second step is required to be performed by a third-party server.
6. The computer system of claim 5 , wherein the first type of data includes data that is accessible by the first server but not the third-party server.
7. The computer system of claim 1 , wherein one or more of the first step and the second step are customizable based on a preference of a publisher of the first step.
8. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system, the one or more programs including instructions for:
identifying electronic data corresponding to an event-based workflow, the electronic data including data corresponding to a first step corresponding to the one or more events and data corresponding to a second step corresponding to one or more events, wherein the first step is different from the second step;
after identifying data corresponding to the event-based workflow, attempting to cause execution of the first step corresponding to the one or more events; and
in response to receiving an indication that execution of the first step corresponding to the one or more events has failed:
in response to determining that the first step is associated with a first set of one or more execution criteria, resolving failure of the first step in a first manner that corresponds to the first set of one or more execution criteria; and
in response to determining that the first step is associated with a second set of one or more execution criteria that is different from the first set of one or more execution criteria, resolving failure of the first step in a second manner that corresponds to the second set of one or more execution criteria, wherein the second manner is different from the first manner.
9. The non-transitory computer-readable storage medium of claim 8 , wherein the first set of one or more execution criteria or the second set of one or more execution criteria is defined as being related to the first step, and wherein the one or more programs include instructions for:
after resolving failure of the first step, attempting to cause execution of the second step corresponding to the one or more events; and
in response to receiving an indication that execution of the second step corresponding to the one or more events has failed, resolving failure of the second step in a third manner that corresponds a third set of one or more execution criteria, wherein the third set of one or more execution criteria is not defined as being related to the first step.
10. The non-transitory computer-readable storage medium of claim 8 , wherein the event-based workflow is a modified version of a preexisting event-based workflow,
wherein the first step is an addition, to the preexisting event-based workflow, made by a third-party that is not the creator of the preexisting event-based workflow, and
wherein the second step is present in the preexisting event-based workflow and is created by the creator of the preexisting event-based workflow.
11. The non-transitory computer-readable storage medium of claim 8 , wherein:
in accordance with a determination that data corresponding to the first step is a first type of data and data corresponding to the second step is a second type of data that is different from the first type of data, the first step is required to be performed by a first server and the second step is required to be performed by a third-party server.
12. The non-transitory computer-readable storage medium of claim 11 , wherein the first type of data includes data that is accessible by the first server but not the third-party server.
13. The non-transitory computer-readable storage medium of claim 8 , wherein resolving failure of the first step in the first manner includes disabling the first step, and wherein the one or more programs include instructions for:
in conjunction with disabling the first step, sending one or more notifications to one or more users, who have indicated that the first step should be performed, that the first step has been disabled.
14. The non-transitory computer-readable storage medium of claim 8 , wherein one or more of the first step and the second step are customizable based on a preference of a publisher of the first step.
15. A method, comprising:
by a computer system:
identifying electronic data corresponding to an event-based workflow, the electronic data including data corresponding to a first step corresponding to one or more events and data corresponding to a second step corresponding to the one or more events, wherein the first step is different from the second step;
after identifying data corresponding to the event-based workflow, attempting to cause execution of the first step corresponding to the one or more events; and
in response to receiving an indication that execution of the first step corresponding to the one or more events has failed:
in response to determining that the first step is associated with a first set of one or more execution criteria, resolving failure of the first step in a first manner that corresponds to the first set of one or more execution criteria; and
in response to determining that the first step is associated with a second set of one or more execution criteria that is different from the first set of one or more execution criteria, resolving failure of the first step in a second manner that corresponds to the second set of one or more execution criteria, wherein the second manner is different from the first manner.
16. The method of claim 15 , wherein the first set of one or more execution criteria or the second set of one or more execution criteria is defined as being related to the first step, and wherein the method further comprises:
after resolving failure of the first step, attempting to cause execution of the second step corresponding to the one or more events; and
in response to receiving an indication that execution of the second step corresponding to the one or more events has failed, resolving failure of the second step in a third manner that corresponds a third set of one or more execution criteria, wherein the third set of one or more execution criteria is not defined as being related to the first step.
17. The method of claim 15 , wherein the event-based workflow is a modified version of a preexisting event-based workflow,
wherein the first step is an addition, to the preexisting event-based workflow, made by a third-party that is not the creator of the preexisting event-based workflow, and
wherein the second step is present in the preexisting event-based workflow and is created by the creator of the preexisting event-based workflow.
18. The method of claim 15 , wherein:
in accordance with a determination that data corresponding to the first step is a first type of data and data corresponding to the second step is a second type of data that is different from the first type of data, the first step is required to be performed by a first server and the second step is required to be performed by a third-party server.
19. The method of claim 18 , wherein the first type of data includes data that is accessible by the first server but not the third-party server.
20. The method of claim 15 , wherein resolving failure of the first step in the first manner includes disabling the first step, and wherein the one or more programs include instructions for:
in conjunction with disabling the first step, sending one or more notifications to one or more users, who have indicated that the first step should be performed, that the first step has been disabled.