You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before, Maestro would call PCS when a code flow subscription was triggered.
Now we can call the code flow logic directly and perform the update.
However, because we are migrating step by step, we are now instead of this just creating a code flow work item which will be picked up by the processor later. This is inefficient but mimics the previous architecture.
Goal
Instead of the async communication back and forth between PCS and Maestro, and instead of the async resolution of code flow subscription triggers by processing it over several work items, we should just execute code flow subscriptions right away.
The text was updated successfully, but these errors were encountered:
Context
Before, Maestro would call PCS when a code flow subscription was triggered.
Now we can call the code flow logic directly and perform the update.
However, because we are migrating step by step, we are now instead of this just creating a code flow work item which will be picked up by the processor later. This is inefficient but mimics the previous architecture.
Goal
Instead of the async communication back and forth between PCS and Maestro, and instead of the async resolution of code flow subscription triggers by processing it over several work items, we should just execute code flow subscriptions right away.
The text was updated successfully, but these errors were encountered: