We are investigating issue that flows generate new IDs which are not possible to set trigger with. It's currently affecting all stacks.
We will update this post as new information becomes available. If you have any questions or concerns, please reach out to our support team.
Update June 05 17:50 UTC We released fix which should solved the issue visually with 201 status response but still the schedule is not available in UI. We will investigate further where is the problem.
Update June 05 18:15 UTC We see things operating as usually. All flows configurations between 17:50 UTC and 18:15 UTC won't be properlly working with triggers.
Also all flows created from ~June 03 15:00 UTC till June 05 17:50 UTC which were created with ULID identifiers remain unusable using table triggers. We will make sure that these will be able to be scheduled with tiggers subsequently. Current approach is to delete your flows with ULID identifiers and create new ones with integer identifiers.
We are sorry for this inconvenience.