What are the Slack Archives?
Itβs a history of our time together in the Slack Community! Thereβs a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you wonβt be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
if you have a state machine with both `time out` and `manually executable`, will it still progress a
Comments
-
to my believe it does.
0 -
you can still have it manually executable to skip timeout imo. not sure if thatβs always a good ideaβ¦
0 -
makes sense if you have something that would otherwise poll every x hours, but you want to override it and make it poll now
0 -
in combination with a condition? yep
0 -
yes exactly
0 -
best though: try it out? π defining timeout to 1m, add condition and manual and see what is supported and what not
0 -
yes yes, i'm being lazy π
0 -
also we noticed it "not working" just now, but would need to investigate more
0 -
also 1m is a long time in dev cycles
0 -
I think itβs not supporting 1s as a setting though π
0 -
not sure I understood how condition is relevant here, but timeout and manual do work for the same event. To have an option βnot to waitβ. Although I never investigated, what happens with timeout entry in DB after you moved the item manually. I guess cron-job will try to process it and skip/remove since itβs not actual any more..
0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
yes.. u can have condition with timeout and the same time with manually flag and it is working..
0 -
but is timeout plus condition actually leading to βpollingβ? meaning: if condition fails and there is no else case, state would stay same. would there be another timeout after configured period? π€ I like the idea, but not sure that this is the case with current spryker OMS
0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
just as example.. we use a lot of cycle in state machine.. of course u need an else state etc... take a look in the example....
0 -
π
0 -
ah this! Yeah, looks familiar to me too, exactly for similar cases. Although we concluded on the project that re-sending the same request multiple times if it fails makes little sense. Rather communicating with βmiddlewareβ, then they find/fix the issue and then we manually retry the transition when theyβre done
0 -
which means the same schema but w/o timeout
0 -
our specific case is less about failure retry, but polling an external system for changes
0 -
yes, this is a good use-case π
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 75 Spryker News
- 924 Developer Corner
- 783 Spryker Development
- 88 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 25 Job Opportunities
- 3.2K π Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random