Happened just today after working fine for months. Don’t know why and don’t have the appetite to fight it.
Testing of the same flow works perfectly fine. It just doesn’t work on its own, and no clear reason because the interface doesn’t give you the details needed to triage. Suspect it’s got something to do with something X changed on their side; but as we said with the Facebook integration fiasco, there’s just not enough triage information on the Activepieces side to resolve.
So we’ve deleted two of our flows and will just do without. The third one will have a new update today; it doesn’t go to X, so if it runs fine, we’ll know that X is the problem.
Hello @CTRStage , Welcome to the community 
,
Check the run logs of the Twitter step from the Activepieces side and see what error is being shown. You can provide the error details here; it will most likely be a 403 error. If you encounter a 403 error, check the status of your Twitter app on the Twitter Developer Dashboard. Verify if the status is live or if the app is suspended or blocked.
Again, the flow was already deleted.
There was nothing wrong on the Twitter side. The test flow worked perfectly fine (that would be using the same conduit).
Saw no specific errors on the Issues page (which is our real beef - not enough triage data on YOUR side to help - for example, “we weren’t able to create the tweet” vs “our side is having a problem right now” or something more specific than just “we ran into an issue”).